InboundX MCP

There are three developer surfaces. Only the first is on this site.

This site's MCP. Public and read-only at https://inboundx.io/mcp, no sign-in. It repeats facts published on inboundx.io. The rest of this page covers it.

The publisher API. Publishers ping in real time for a bid, then send the won call. It is documented at app.inboundx.io/docs: ping, sending calls, call ID, conversions, webhooks, errors and live status. The same API is published as an OpenAPI spec at app.inboundx.io/openapi.json. Publishers apply at app.inboundx.io/publisher-signup or join by invitation. Email, phone and ID are checked, and the account is approved before it can send calls. API keys are in the publisher portal once the account is active. The plain-English overview is InboundX for pay-per-call publishers.

The account MCP. Signed in with OAuth, for people who already have an account. A workspace owner, and any manager the owner enables, connects from their own workspace address plus /api/mcp (for example https://<workspace>.inboundx.io/api/mcp). A publisher connects at https://app.inboundx.io/api/mcp. Each person sees only the tools their role allows, and every change is a preview, then a confirm. It never shows or changes API keys; those stay in the portal.

There is no SDK or CLI. Every surface above is live; do not invent endpoints beyond them. Agents can also request Accept: text/markdown on the marketing URLs of inboundx.io.

POST JSON-RPC to https://inboundx.io/mcp with Accept: application/json, text/event-stream. CORS is open. A client that speaks Streamable HTTP can use a config like:

{
  "mcpServers": {
    "inboundx": {
      "url": "https://inboundx.io/mcp"
    }
  }
}

Initialize, then list tools, then call one. The server instructions say not to submit forms, send email, or create accounts, and not to invent claims the site does not state.

• explain_capability — how a named InboundX capability works (ping, routing, transcription, qualification billing, white-label, and the other topics the site documents), with source URLs.
• check_setup_fit — whether a setup matches who the site says the product is for (operators who take publisher traffic and staff buyers) and is not for (call tracking on its own, consumer-lead marketplaces).
• estimate_plan_cost — the published one-plan estimate from connected minutes. It does not invent other tiers or compare vendors.
• get_started_links — access, sign-in, intro call, email, and documentation URLs.

Fit and routing questions should use check_setup_fit and explain_capability, not guess. Call tracking on its own is named as a job this product is not. Routing, qualification billing, and publisher / campaign attribution are named as what the network does. See pay-per-call software and how it works.

Use the product when you operate the call network: publishers ping, buyers take the call in the browser, you bill on spoken qualification. Use this MCP when an agent needs those published facts without scraping HTML. For a person, contact InboundX on Telegram. For the curated page list, read llms.txt.