Pax8 MCP Server

Pax8 MCP is an MCP integration. Every Pax8 Partner API endpoint, plus an offline store that reconciles billing, tracks MRR, and.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/pax8-v0.1.4/pax8-mcp.mcpb, version 0.1.4. Its declared MCP transport is stdio.

The package declares PAX8_AUDIENCE: OAuth2 audience claim requested when minting the Pax8 token. The default is the partner API audience; change it only if Pax8 told you to.; PAX8_BASE_URL: Base URL for the Pax8 API. Leave the prefilled default unless your account uses a different regional or self-hosted host.; PAX8_CLIENT_ID (required): Pax8 Partner API OAuth2 Client ID (Pax8 portal > Integrations).; PAX8_CLIENT_SECRET (required): Pax8 Partner API OAuth2 Client Secret (Pax8 portal > Integrations).; PAX8_OAUTH_SCOPE (required): Optional OAuth2 scope; omitted from the token request when unset.; PAX8_TOKEN_URL: Token endpoint the client-credentials exchange posts to. Leave the prefilled default unless your tenant uses a different token endpoint.; PAX8_NO_CONFIG_WRITE: Set to 1 to keep credentials off disk. The token cache becomes a no-op, so the connector mints a fresh token each run instead of writing one to config.toml. Leave blank for the default cached behaviour..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.4 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.