Connect Pax8 to Conduit

This walkthrough connects Pax8 (sales/marketplace) to Conduit. Pax8 is one of the few vendors that runs its own hosted MCP server — Conduit proxies your calls to https://mcp.pax8.com/v1/mcp rather than to a Conduit-run integration container. You generate a legacy MCP token in the Pax8 app, then add it as an organization connection in Conduit.

Use Conduit’s Pax8 connection. Do not also paste the Claude Desktop (or Cursor / Copilot) config from app.pax8.com/integrations/mcp into your AI client. That config talks to Pax8 directly and skips Conduit’s access grants and audit log. Pax8’s page offers OAuth 2.0 as the recommended client setup and a legacy token as the other option. Conduit uses the legacy token today (a UUID, sent as x-pax8-mcp-token). An OAuth access token will not work in the MCP Token field.

Menu labels can change

The Pax8 steps below reflect the current app flow; menu labels can shift between releases. If a label differs, see Pax8’s MCP server docs — they are the authority for this flow.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A Pax8 login with access to the integrations area of app.pax8.com.

Step 1 — Generate an MCP token in Pax8

1. Sign in to Pax8 and go to app.pax8.com/integrations/mcp. Expected: the MCP token page.
2. Generate an MCP token (see Pax8’s MCP server docs for details). Expected: a token value, shown at creation.
3. Copy the token immediately.

Caution

Copy the token now and store it somewhere safe. Don’t paste it into chat, email, or a shared document — the next step moves it directly into Conduit, which encrypts it at rest. If you accidentally expose the token, revoke it and generate a new one at app.pax8.com/integrations/mcp first; the exposed token becomes useless immediately.

Step 2 — Connect Pax8 in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Pax8 in the catalog (under Sales) and click Connect. Expected: a credential form with a single MCP Token field (placeholder: “Generate at app.pax8.com/integrations/mcp”).
3. Paste the token from Step 1 into the MCP Token field (required).
4. Click Connect. Expected: Conduit performs a real MCP handshake with Pax8’s hosted server using your token and shows Connected — the same call path your live tool calls will use. A bad token is rejected here, not on the first tool call.

The credential is stored at the organization scope, so every technician in your org shares this Pax8 connection. (For per-technician tokens, connect at the personal scope instead — see Vendor connections.)

Verify it worked

Connect an MCP client to Conduit (see Connecting an AI client) and ask it to run a read-only Pax8 tool, such as listing companies or subscriptions. Real data should come back, and the call appears in your audit log with vendor pax8.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid Pax8 MCP token. Generate one at app.pax8.com/integrations/mcp.”	The token was mistyped, revoked, or isn’t an MCP token (a regular Pax8 API credential won’t work here). Generate a fresh MCP token and re-connect.
Connect fails with “Pax8 MCP server returned HTTP …”	Pax8’s hosted MCP server responded with an unexpected status — usually transient on the Pax8 side; retry, then check Pax8’s MCP docs for service notices.
Tool calls return 403 “no credentials for vendor”	Pax8 isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a token.
Need to rotate the token	Generate a new MCP token at app.pax8.com/integrations/mcp, then update the credential at /org/catalog.
The access card lists Pax8 tools, but the AI client’s tool list does not include them	The access card shows Conduit’s classified catalog. The client only receives tools after a live tools/list to Pax8. A 401 (revoked token, or a value that is not the legacy UUID token) drops Pax8 from that list while the card still shows the catalog. Generate a fresh legacy MCP token and reconnect. Do not add Pax8’s own Claude Desktop config alongside Conduit.
Connect fails with “That is not a Pax8 legacy MCP token…”	The value is not the legacy UUID token. Pax8’s portal recommends OAuth 2.0 for Claude Desktop; Conduit does not use that path. Generate the token on the MCP page and paste only that UUID. Do not add Pax8’s Claude Desktop config next to Conduit.

Related

• Vendor connections — credential scopes, rotation, and the full vendor catalog.
• Security — how Conduit encrypts and resolves the credential you just stored.