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/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/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

In ChatGPT, add a connector / custom MCP server pointing at the streamable-HTTP endpoint with bearer auth:

{
  "name": "BusinessMCP",
  "transport": "http",
  "url": "https://businessmcp.com/api/mcp/mcp",
  "authorization": "Bearer mcph_your_key_here"
}

Once added, ChatGPT can discover and call your tools during a conversation just like any other connector.

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/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/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, create_task 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.