pax8-mcp
Based on the provided schema, this stateless MCP server lets AI clients perform read-only/list-style queries against the Pax8 Partner API using a per-request X-Pax8-Token.
List companies, with pagination, sorting, and optional name filtering.
List contacts for a specified company.
List subscriptions, with pagination, sorting, and filters for company, status, and product.
List usage summaries for a subscription and usage lines for a usage summary.
List invoices and invoice line items, with company/status filters and pagination.
List orders, with company/status filters and pagination.
List Pax8 marketplace products, with vendor/product name filters and pagination.
Note: the provided schema does not include the README-described single-item get or subscription update tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@pax8-mcp list my active subscriptions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pax8-mcp
Stateless HTTP MCP service for the Pax8 Partner API. Exposes Pax8 data as MCP tools so AI assistants can query companies, subscriptions, invoices, orders, products, and usage data.
MSPbots Connector
The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.
Get started at connect.mspbots.ai →
MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.
Hosted service: connect.mspbots.ai · Free to use.
Why Connector

Visible | Every tool call is logged: who, which vendor, when. Usage dashboard, CSV export, SIEM streaming. |
Controlled | Role-based, per-tool allowlist. Deny by default. |
Protected | Credentials encrypted per record. AI clients never see your vendor passwords or tokens. |
MSP-native | Built for the MSP stack only: RMM, PSA, documentation, security, finance. |
Quick start
Sign up at connect.mspbots.ai.
Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.
Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.
Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.
Ask your AI to do real work, and watch every call appear in the audit log.
Features
Unified gateway
One MCP URL for all your AI clients
150+ connectors across the MSP stack
Custom MCP servers supported, free
Authorization happens on each vendor's own page; the AI never sees passwords or tokens
Bring your own credentials: use the vendor API keys you already have
Multiple accounts per app; connect once, reuse across AI clients
Tool search: finds the right action for the task
One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically
Visibility
Audit log for every tool call (who, which vendor, when)
Usage dashboard: call volume, top vendors, error rate, per-user activity
Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)
Optional recording of tool arguments and result summaries (off by default, enabled per organization)
Control
Per-role, per-tool allowlist, deny by default
owner / admin / member roles
SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace
Security
Credentials encrypted one record at a time (AES-256-GCM, per-record key)
AI clients authenticate with OAuth 2.1 + PKCE
Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.
Static egress IP for customer firewall and API allowlisting
Pricing
Free.
Links: connect.mspbots.ai · mspbots.ai
Related MCP server: Microsoft Business Central MCP Server
Architecture
Stateless — no user state or credentials stored between requests
Per-request auth — access token passed via
X-Pax8-Tokenheader on every callConcurrent-safe — Python
contextvarsisolate credentials across parallel requestsTransports — HTTP (production) or stdio (development)
Endpoints
Endpoint | Description |
| MCP protocol entry point (JSON-RPC) |
| Health check |
Default port: 8080
Authorization
Pass your Pax8 access token in every /mcp request:
X-Pax8-Token: <your_access_token>The service forwards the token as Authorization: Bearer <token> to the Pax8 API. Tokens are never stored globally — each request is fully isolated.
Tool List
Tool | Description | Key Parameters |
| List companies in the partner account |
|
| List contacts for a company |
|
| Get a single company by id |
|
| List subscriptions |
|
| Get a single subscription by id |
|
| List usage summaries for a subscription |
|
| Update a subscription's quantity, billing term, or dates |
|
| List invoices |
|
| List line items for an invoice |
|
| List orders |
|
| List products in the Pax8 marketplace |
|
| Get a single product by id (name, vendor, SKU) |
|
| List usage lines for a usage summary |
|
Parameter Details
Pagination (all list tools):
page— zero-based page number (default:0)size— results per page (default:10)sort— field and direction, e.g."name,asc"or"createdDate,desc"
pax8_list_subscriptions status values:
Active, Cancelled, PendingManual, PendingAutomated, PendingCancel, Terminated, Expired, Trial
pax8_update_subscription billing_term values:
Monthly, Annual, 2-Year, 3-Year, 1-Time, Trial
Quick Start
Local development (env mode)
# Copy and edit environment config
cp .env.example .env
# Set PAX8_API_TOKEN and AUTH_MODE=env in .env
# Install dependencies
uv sync
# Run the server
MCP_TRANSPORT=http AUTH_MODE=env python -m pax8_mcpDocker (gateway mode — production)
docker build -t pax8-mcp .
docker run -p 8080:8080 -e AUTH_MODE=gateway pax8-mcpOr with Docker Compose:
docker compose upTest Examples
Health check:
curl http://localhost:8080/health
# {"status":"ok","transport":"http","auth_mode":"gateway"}List companies:
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "X-Pax8-Token: <your_access_token>" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "pax8_list_companies",
"arguments": {"page": 0, "size": 5}
}
}'List subscriptions for a company:
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "X-Pax8-Token: <your_access_token>" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "pax8_list_subscriptions",
"arguments": {"company_id": "<company_uuid>", "status": "Active"}
}
}'List invoice items:
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "X-Pax8-Token: <your_access_token>" \
-d '{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "pax8_list_invoice_items",
"arguments": {"invoice_id": "<invoice_uuid>"}
}
}'List usage lines for a usage summary:
curl -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "X-Pax8-Token: <your_access_token>" \
-d '{
"jsonrpc": "2.0",
"id": 4,
"method": "tools/call",
"params": {
"name": "pax8_list_usage_summary_lines",
"arguments": {"usage_summary_id": "<usage_summary_uuid>"}
}
}'Configuration Reference
Variable | Default | Description |
| — | Access token (env mode only) |
|
| Pax8 API base URL |
|
| MCP request header carrying the token |
|
|
|
|
| HTTP listen port |
|
| HTTP listen host |
|
|
|
Available Tools
9 toolspax8_list_companiesA
List companies in the Pax8 partner account.
Args:
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
sort: Sort field and direction, e.g. "name,asc" or "createdDate,desc".
name: Filter companies by name (partial match).
Inputs: name, page, size, sort. Returns: result
pax8_list_company_contactsA
List contacts for a specific company.
Args:
company_id: The unique identifier of the company.
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
Inputs: company_id (required), page, size. Returns: result
pax8_list_invoice_itemsA
List line items for a specific invoice.
Args:
invoice_id: The unique identifier of the invoice.
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
Inputs: invoice_id (required), page, size. Returns: result
pax8_list_invoicesA
List invoices in the Pax8 partner account.
Args:
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
sort: Sort field and direction, e.g. "invoiceDate,desc".
company_id: Filter by company ID.
status: Filter by invoice status, e.g. "Paid", "Unpaid", "Overdue".
Inputs: page, size, sort, status, +1 more. Returns: result
pax8_list_ordersC
List orders in the Pax8 partner account.
Args:
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
sort: Sort field and direction, e.g. "orderDate,desc".
company_id: Filter by company ID.
status: Filter by order status, e.g. "Pending", "Completed", "Cancelled".
Inputs: page, size, sort, status, +1 more. Returns: result
pax8_list_productsA
List products available in the Pax8 marketplace.
Args:
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
sort: Sort field and direction, e.g. "productName,asc".
vendor_name: Filter by vendor name (partial match).
product_name: Filter by product name (partial match).
Inputs: page, size, sort, vendor_name, +1 more. Returns: result
pax8_list_subscriptionsA
List subscriptions in the Pax8 partner account.
Args:
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
sort: Sort field and direction, e.g. "startDate,asc".
company_id: Filter by company ID.
status: Filter by subscription status. One of: Active, Cancelled,
PendingManual, PendingAutomated, PendingCancel, Terminated, Expired, Trial.
product_id: Filter by product ID.
Inputs: page, size, sort, status, +2 more. Returns: result
pax8_list_subscription_usage_summariesB
List usage summaries for a specific subscription.
Args:
subscription_id: The unique identifier of the subscription.
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
Inputs: subscription_id (required), page, size. Returns: result
pax8_list_usage_summary_linesA
List usage lines for a specific usage summary.
Args:
usage_summary_id: The unique identifier of the usage summary.
page: Zero-based page number for pagination (default: 0).
size: Number of results per page (default: 10).
Inputs: usage_summary_id (required), page, size. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct entity (companies, contacts, invoices, subscriptions, etc.), so there is no overlap or ambiguity in purpose.
All tools follow the exact same pattern 'pax8_list_<entity>', with clear and consistent naming conventions.
With 9 tools, the set is well-scoped for a read-only listing API, covering all major data entities without excess.
The tool surface covers listing for all main entities but lacks any retrieval by ID, creation, update, or delete operations, making it incomplete for full CRUD/lifecycle coverage typical of a domain API.
Maintenance
Related MCP Connectors
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceA unified HTTP/HTTPS service that exposes Model Context Protocol (MCP) functionality over HTTP endpoints, allowing clients to list available tools and call them through a standardized API.10 npm-
- AlicenseAqualityCmaintenanceModel Context Protocol (MCP) server for Microsoft Dynamics 365 Business Central. Provides AI assistants with direct access to Business Central data through properly formatted API v2.0 calls.63,422 npm10MIT
- FlicenseAqualityDmaintenanceProvides reusable MCP tools for Amazon Connect AI Agents and Bedrock AgentCore to look up customers, manage support tickets, schedule appointments, update CRM records, retrieve knowledge, and create tasks.7-
- FlicenseNot gradedqualityCmaintenanceExposes the Ravex Partner API to MCP-compatible AI agents, with secure bearer-token authentication, idempotent write operations, and webhook-based reconciliation for async processing.-