MCP config generator
Hand-writing claude_desktop_config.json is the #1 source of "my MCP server doesn't show up". Generate valid config for Claude Desktop, Cursor, or VS Code — remote servers, npm packages, and your BusinessMCP endpoint — in seconds.
Any remote MCP server (streamable HTTP)
Any npm MCP server (stdio)
claude_desktop_config.json
{
"mcpServers": {
"businessmcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://businessmcp.com/api/mcp",
"--header",
"Authorization: Bearer mcph_YOUR_KEY_HERE"
]
}
}
}macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json — restart Claude Desktop fully after saving.
Find servers worth connecting
Browse the MCP server directory for 200+ servers with real capabilities and example prompts, or follow the Claude Desktop setup guide for the full walkthrough including troubleshooting.
Frequently asked questions
Why does the Claude Desktop config use mcp-remote for HTTP servers?
Claude Desktop’s config file natively launches stdio servers (a command + args). mcp-remote is the standard bridge: it runs as a stdio process locally and proxies to your remote streamable-HTTP server, handling auth headers reliably across app versions. Claude’s built-in Connectors UI can also add remote servers directly — both routes work.
Where do the config files go?
Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows — then fully restart the app. Cursor: .cursor/mcp.json in the project or ~/.cursor/mcp.json globally. VS Code: .vscode/mcp.json in the workspace.
My server doesn’t show up after saving — what now?
The usual culprits: invalid JSON (trailing commas), the app not FULLY restarted (quit from the tray/dock, not just the window), or npx not on the PATH the app sees (use an absolute path to node/npx). Our Claude Desktop setup guide has the full troubleshooting matrix.
What can I connect with a BusinessMCP key?
Your entire business: analytics, identified visitor companies, CRM, revenue, ads, and SEO data — exposed as one MCP endpoint any Claude/GPT/Gemini client can query, with scoped access policies controlling what each key can see.