How to Connect Claude Desktop to Your Business MCP Server

Claude Desktop is powerful out of the box, but on its own it has no idea what is happening inside your business. It cannot see how many visitors converted yesterday, which ad campaign is bleeding money, or which customer just churned. The Model Context Protocol (MCP) closes that gap: it is an open standard that lets an AI client like Claude Desktop call live tools and read live data from an external server you control.

BusinessMCP turns your entire company into exactly that kind of server. You connect your tools, databases, ad platforms and Stripe revenue once, install a single tracking script, and we unify everything into one hosted MCP endpoint. When you point Claude Desktop at that endpoint, Claude stops guessing and starts answering from your real numbers — the same numbers your dashboard shows.

The result is a single, model-agnostic source of truth. The endpoint you connect to Claude today works identically with GPT, Gemini, or any other MCP-capable agent tomorrow. You are never re-plumbing your data for a new model.

You need three things: a BusinessMCP workspace, at least the tracking script installed so events are flowing, and a Claude Desktop install on macOS or Windows. If you have not onboarded yet, the wizard walks you through the business context, goals and the one required step — pasting the tracking snippet onto your site.

You also need an API key. In BusinessMCP these are Bearer keys prefixed with mcph_ and scoped to a single workspace. Generate one from Settings, treat it like a password, and never commit it to a public repo. The key is what authorizes Claude Desktop to read your unified data through the /api/mcp endpoint.

Optionally, connect a few source tools first — Stripe, Google Search Console, your ad accounts — so there is richer data for Claude to query on day one. None of these are required to get a working connection, but they make the first conversation far more useful.

Claude Desktop reads MCP servers from a JSON config file. On macOS it lives at ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it is under %APPDATA%\Claude\. Open it in any text editor — if the file does not exist yet, create it.

Add an entry under the mcpServers key that points at your BusinessMCP endpoint and passes your Bearer key. Because BusinessMCP speaks the streamable HTTP transport, you point Claude at the hosted URL rather than a local command. A minimal config names the server, sets the URL to your workspace endpoint at /api/mcp, and includes an Authorization header of "Bearer mcph_your_key_here".

Save the file and fully quit Claude Desktop — not just close the window, but quit the app so it reloads the config. When it restarts, you should see your BusinessMCP server listed in the tools menu, usually shown as a small plug or hammer icon in the message composer.

Start a new chat and ask something only your business data could answer: "How many visitors did we get this week and what was the conversion rate?" Claude will call the analytics tool on your MCP server, receive the numbers, and answer in plain language. If you see a tool-use indicator followed by a real figure, the connection is live.

If Claude says it cannot access any tools, the usual culprits are a malformed JSON config, a stale key, or the app not being fully restarted. Re-check that your Bearer key is current, that the URL ends in /api/mcp, and that the JSON has no trailing commas. BusinessMCP also logs every tool call, so you can confirm from the dashboard whether the request ever reached the server.

Once verified, the whole surface of your business is available conversationally. Ask Claude to pull ROAS by campaign, summarize new leads, or draft a follow-up email to a customer — each of those maps to a real tool on your hosted endpoint.

Your mcph_ key is a bearer credential: anyone who holds it can read your workspace data. Store it in a password manager, rotate it if it ever leaks, and use a separate key per machine or per agent so you can revoke one without breaking the others. BusinessMCP scopes each key to a single workspace and honors row-level security, so a key can never reach another tenant.

For shared or automated setups, prefer generating a dedicated key rather than reusing your personal one. When someone leaves the team or a laptop is lost, revoking that single key instantly cuts off access without disturbing anyone else.