MCP Clients Compatibility Matrix
Hands-on comparison of how the major AI clients handle remote MCP servers: transports, OAuth 2.1 onboarding (DCR / CIMD), custom auth headers and interactive MCP Apps (ui://). Last verified November 2026.
| Client | Streamable HTTP | Legacy SSE | OAuth DCR | CIMD | Custom Headers | MCP Apps (ui://) | Config / Setup |
|---|---|---|---|---|---|---|---|
| Cursor | β | β | β | β οΈ Partial | β | β | ~/.cursor/mcp.json Β· guide β |
| Claude Code (CLI) | β | β | β | β οΈ Partial | β | β | claude mcp add --transport http Β· guide β |
| Claude.ai (Web & Mobile) | β | β | β | β | β | β | Settings β Connectors β Add custom connector Β· guide β |
| Claude Desktop | β οΈ via mcp-remote | β οΈ via mcp-remote | β | β | β οΈ via mcp-remote | β | claude_desktop_config.json (mcpServers) Β· guide β |
| VS Code (GitHub Copilot) | β | β | β | β οΈ Partial | β | β | .vscode/mcp.json (servers) Β· guide β |
| ChatGPT Connectors | β | β | β οΈ Partial | β | β | β | Settings β Connectors β Advanced β Developer Mode Β· guide β |
| Kiro (AWS IDE) | β | β | β | β οΈ Partial | β | β | ~/.kiro/settings/mcp.json Β· guide β |
| Windsurf | β | β | β οΈ Partial | β | β | β οΈ Partial | ~/.codeium/windsurf/mcp_config.json Β· guide β |
| OpenAI Codex CLI | β | β | β οΈ Partial | β | β | β | ~/.codex/config.toml ([mcp_servers]) Β· guide β |
| Cline | β | β | β οΈ Partial | β | β | β οΈ Partial | cline_mcp_settings.json (mcpServers) Β· guide β |
| Gemini CLI | β | β | β οΈ Partial | β | β | β | ~/.gemini/settings.json (mcpServers httpUrl/url) Β· guide β |
| Zed | β | β | β οΈ Partial | β | β | β οΈ Partial | settings.json (context_servers) |
β οΈ mcp-remote = stdio bridge (npx -y mcp-remote <url>) for clients without native remote support β generate the config at /mcp-remote. βPartialβ = works but with caveats (manual client_id, evolving support, or limited scope).
Frequently Asked Questions
Which MCP clients support Streamable HTTP natively?
Cursor, Claude Code, Claude.ai, VS Code, ChatGPT Connectors, Kiro, Windsurf, Codex CLI and Zed all speak Streamable HTTP natively. Claude Desktop is the main exception β it is stdio-only, so remote servers go through the `npx -y mcp-remote <url>` bridge. Generate a ready-made config at /mcp-remote.
Which clients render interactive MCP Apps (ui://)?
Claude (web, desktop and Code), VS Code and ChatGPT render ui:// interactive widgets inline in the conversation. Kiro also supports them. Other clients fall back to plain tool calls.
How do I connect OAuth 2.1 remote MCP servers in clients without native support?
Clients with Dynamic Client Registration (DCR) β Cursor, Claude Code, VS Code, Kiro β can register themselves automatically. Without DCR you must pre-register a client_id with the provider, or use mcp-remote which performs its own local OAuth flow and opens a browser for consent. Test any endpoint's full OAuth setup in /oauth-debugger.
What is CIMD (Client ID Metadata Document)?
CIMD lets a client publish its identity as an HTTPS URL instead of registering: the authorization server fetches the client_id URL to read the metadata document. It removes the need for per-user DCR. This site publishes one at /.well-known/oauth-client.json for its online inspector.
Where do I put the config file for my client?
Cursor: ~/.cursor/mcp.json Β· VS Code: .vscode/mcp.json or user settings Β· Kiro: ~/.kiro/settings/mcp.json Β· Windsurf: ~/.codeium/windsurf/mcp_config.json Β· Codex CLI: ~/.codex/config.toml Β· Cline: cline_mcp_settings.json Β· Gemini CLI: ~/.gemini/settings.json Β· Claude Desktop: claude_desktop_config.json (paths vary by OS β see /mcp-remote) Β· Claude Code: `claude mcp add` command Β· Claude.ai & ChatGPT: web UI connectors, no file needed.