β‘ MCP Config & mcp-remote Generator
Pick any server from the registry β or paste a custom endpoint β and get ready-to-paste client configs for claude_desktop_config.json (via the mcp-remote stdio bridge), Cursor, VS Code, Claude Code, Kiro and Windsurf. Tokens are processed locally in your browser only.
Select a server above (or choose Custom endpoint) to generate configs for all 6 clients.
π claude_desktop_config.json β exact file paths
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Remote servers go under the mcpServers key and use the npx -y mcp-remote <url> bridge, because Claude Desktop only speaks stdio transports.
π§ mcp-remote troubleshooting
Node.js β₯ 20 required
mcp-remote runs through npx β check `node -v` first. On older Node versions you'll see 'unsupported engine' or silent connection failures.
Passing headers
Use --header "Authorization: Bearer <token>" (repeatable). The header value must follow the flag with a space β quoted values containing spaces need the whole string quoted.
Stale OAuth cache
If a previously-authorized server keeps 401ing or shows a dead consent flow, clear ~/.mcp-auth (or the per-server folder inside it) and re-run β the stored refresh token is probably revoked.
When to skip mcp-remote entirely
If your client supports remote servers natively (Cursor, VS Code, Claude Code, Windsurf, Kiro, ChatGPT connectors), point it straight at the Streamable HTTP URL. mcp-remote exists for stdio-only clients like Claude Desktop.
Session / SSE weirdness
For legacy SSE servers append --transport sse. For Streamable HTTP servers the bridge handles protocol negotiation itself β no flag needed.