Connect Claude, GPT & Gemini to your MCP endpoint

Before you start

You need two things: your endpoint URL and a Bearer mcph_* key. The URL is the same for everyone — https://businessmcp.com/api/mcp — and the key comes from Settings in your dashboard (see expose your MCP endpoint). Because MCP is a standard, the setup below is nearly identical across clients: give the client the URL, hand it the bearer token, done. This is the whole point of a model-agnostic layer — connect once, use everywhere.

Claude Desktop

Add your endpoint to Claude Desktop's config file (claude_desktop_config.json):

{
  "mcpServers": {
    "businessmcp": {
      "type": "http",
      "url": "https://businessmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mcph_your_key_here"
      }
    }
  }
}

Restart Claude Desktop and your workspace's tools appear in the tool menu. Ask "what were my top channels last week?" and Claude will call get_analytics against your data.

ChatGPT and Claude.ai

Both add connectors through their own UI rather than a config file, and both authenticate over OAuth — neither has a field for pasting a Bearer token. So you do not need a mcph_* key for these two: paste the endpoint URL, and you will be sent to BusinessMCP to sign in and choose how much access to grant.

https://businessmcp.com/api/mcp

On the consent screen you pick an access level. Choosing a scoped policy means the connector can only reach the data classes that policy allows — so you can hand ChatGPT read-only analytics while keeping revenue and contact details out of it. Manage or revoke the resulting key later in Settings → API & Vault.

Config-file clients (Claude Desktop, Claude Code, Cursor, VS Code) use the Bearer key instead — see the sections above and below.

Cursor

Cursor reads MCP servers from its settings. Add an HTTP server with your URL and bearer header:

{
  "mcpServers": {
    "businessmcp": {
      "url": "https://businessmcp.com/api/mcp",
      "headers": { "Authorization": "Bearer mcph_your_key_here" }
    }
  }
}

Now your coding agent can pull real business context — analytics, CRM, campaigns — into the same window where you write code.

Gemini & custom agents

Any client that speaks MCP works. For clients that only support the stdio transport, run a small local bridge that forwards stdio to your HTTP endpoint:

{
  "mcpServers": {
    "businessmcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://businessmcp.com/api/mcp",
        "--header", "Authorization: Bearer mcph_your_key_here"
      ]
    }
  }
}

For a fully custom agent, use your MCP SDK's HTTP client, set the endpoint URL, and attach the Authorization: Bearer mcph_... header on every request. The discovery-then-invoke flow is identical to the raw calls in expose your MCP endpoint.

Verify the connection

Whichever client you use, confirm two things. First, that discovery works — the client should list tools like get_analytics, list_contacts and your connector tools (github_*, gsc_*). Second, that a real call returns data. Ask a question that forces a tool call and check the answer reflects your actual numbers. If discovery fails, it is almost always the header: confirm the key is current, prefixed mcph_, and sent as a bearer token.