InnerVault

Pax8 MCP

Stale Official MCP Registry, io.github.Servosity

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

Open the source (opens github.com) https://github.com/servosity/msp-skills

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: PAX8_CLIENT_ID, PAX8_CLIENT_SECRET, PAX8_MCP_HTTP_TOKEN, PAX8_OAUTH_SCOPE, PRINTING_PRESS_CLIENT_PROFILE. Use a key with the least access you can.

What it is

MCP servers from io.github.Servosity.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

mcpb package (stdio)

https://github.com/Servosity/msp-skills/releases/download/pax8-v0.1.13/pax8-mcp.mcpb@0.1.13

From the server's entry in the official MCP Registry

Settings it asks for

  • 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 secret required · Pax8 Partner API OAuth2 Client ID (Pax8 portal > Integrations).
  • PAX8_CLIENT_SECRET secret required · Pax8 Partner API OAuth2 Client Secret (Pax8 portal > Integrations).
  • PAX8_OAUTH_SCOPE secret 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: the client ID and secret go only to Pax8's token manager or your API…
  • 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…
  • PRINTING_PRESS_CLIENT_PROFILE secret · Optional: binds the MCP server to an existing tenant-gated Printing Press client profile. Leave unset for a single-tenant install.
  • PAX8_MCP_READ_ONLY · Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing call.
  • PAX8_NO_LOCAL_DATA · Optional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.
  • PAX8_USER_AGENT · Overrides the User-Agent the CLI sends on Pax8 requests.
  • PAX8_MCP_HTTP_TOKEN secret · Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.

Related

  1. MSPStuff Switchboard

    MCP servers

    Hosted MCP servers for MSP tools: ConnectWise, NinjaOne, Microsoft 365, SentinelOne, Pax8 and more.

    Stale Official MCP Registry, io.mspstuff Updated 44 days ago 1 note

  2. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  3. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  4. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  5. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  6. Anthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.

    Hand-checked InnerVault (hand-checked), Anthropic Anthropic documentation