Several coding assistants document MCP server connections, but the setup and supported capabilities differ by client. This checked-November 3, 2026 reference links current product setup pages for Claude Code, Codex, Cursor, Cline, Continue, and GitHub Copilot in VS Code. Use each product’s own docs to confirm the transport, configuration scope, and organization controls for your setup.
Which coding assistants document MCP client support?
| Client | What its documentation confirms | Setup and reference |
|---|---|---|
| Claude Code | Connects to MCP servers and documents remote HTTP/SSE, local stdio, configuration scopes, server approvals, and status checks. | Anthropic MCP reference |
| Codex CLI and IDE extension | Can connect to MCP servers; the official OpenAI Docs MCP quickstart shows CLI setup and says CLI and IDE configuration is shared. | OpenAI Docs MCP quickstart |
| Cursor | Documents MCP tools, prompts, roots, and elicitation, plus stdio, SSE, and Streamable HTTP transports. | Cursor MCP guide |
| Cline | Documents local stdio and remote HTTP/SSE servers, with separate CLI and IDE setup paths. | Cline MCP guide |
| Continue | Documents MCP server configuration for its agent mode. | Continue MCP setup |
| GitHub Copilot in VS Code | Documents adding MCP servers over HTTP or stdio. Configuration choices and capabilities vary by selected agent harness and policy. | VS Code MCP setup; manage and troubleshoot |
This is a selected directory of coding clients, not a complete list of MCP implementations or a feature-equivalence table. “Documents MCP support” means a linked first-party guide describes connecting MCP servers; it does not guarantee that every server, transport, capability, plan, or organization configuration works in every client.
Why can one MCP server behave differently across clients?
The Model Context Protocol standardizes communication, but the host application determines which capabilities it exposes and how a server is configured, approved, authenticated, or enabled. A May 2025 Cursor community thread describes a user expecting Cursor to discover a server configured for Claude Desktop; a Cursor staff reply said automatic discovery was not then available. Treat that report as an example of a setup mismatch, not a statement about current Cursor behavior. Check the current client docs linked above.
For each server you want to reuse, compare the client’s expected config file and format, supported transport, credentials and OAuth path, workspace or user scope, approval controls, and organization policy. Verify the connection in the client’s own status or tools view, then make one low-risk test call. A copied configuration is not proof that the server started or that the intended tools are available.
What does the official MCP client directory establish?
The MCP project’s former clients page now redirects to the general documentation, as checked November 3, 2026. Its linked client matrix is in a repository GitHub marks archived on April 8, 2025. That historical matrix lists clients including Claude Code, Cline, Continue, Cursor, and VS Code GitHub Copilot, but it should not be used as a current support guarantee. This page therefore links each selected product’s own documentation and reports no unsupported-feature inference from the old matrix.
How was this client reference assembled?
Selection was limited to coding assistants already covered by this site and for which a first-party MCP setup guide was found. The former MCP clients catalog was checked as a discovery source, not treated as current product documentation; current vendor documentation was checked November 3, 2026. The Cursor community thread is included only as qualitative evidence that people encounter cross-client setup questions. No compatibility tests were run, and no search-volume, quality, or security ranking is implied.
Frequently asked questions
Does MCP support mean the same features in every client?
No. Check the client’s current documentation for supported transports, capabilities, authentication, configuration scope, approval behavior, and policy limits. The protocol name alone does not establish feature parity.
Can I copy one client’s MCP configuration into another?
Not safely without checking the target format and requirements. Clients may use different configuration files, field names, transport options, and credential mechanisms. Use the target client’s official setup guide and verify a tool call.
Is the MCP project’s old client matrix current?
The linked GitHub repository is marked archived, and the former /clients URL redirects to general MCP documentation. Treat that matrix as historical discovery material and confirm current support in product documentation.
Does this page test MCP compatibility?
No. It records first-party setup documentation and one qualitative client-setup discussion. It does not connect clients to servers or test transports, authentication, capabilities, or reliability.
Sources · checked November 3, 2026
- Model Context Protocol: former clients directory URL — redirects to the current general documentation.
- MCP documentation repository: archived clients matrix — historical client discovery; GitHub marks the repository archived April 8, 2025.
- Anthropic Claude Code: Connect to tools via MCP — setup, transports, scopes, and approval behavior.
- OpenAI Developers: Docs MCP — Codex CLI and IDE setup instructions.
- Cursor: Model Context Protocol — current MCP capability and configuration documentation.
- Cline: MCP — current CLI, extension, local, and remote setup instructions.
- Continue: How to Set Up MCP — configuration and agent-mode scope.
- Visual Studio Code: Add MCP servers — setup formats, transports, policy, and verification.
- Visual Studio Code: Manage and troubleshoot MCP servers — harness-specific configuration and limits.
- Cursor Community: “Can we use MCP from Claude Desktop in Cursor?” — one historical qualitative report, posted May 24, 2025.
Related: Claude Code MCP proxy troubleshooting, Claude Code vs Codex workflows, and the coding-assistant directory.
Methodology and limitations
Selected coding clients already covered by this site with first-party MCP setup documentation checked November 3, 2026. The former MCP clients directory URL now redirects to general documentation; its linked GitHub matrix is treated as historical discovery only because GitHub marks that repository archived April 8, 2025. One Cursor community thread is cited as qualitative evidence of cross-client setup questions. No compatibility tests, search-volume estimates, or feature rankings were made.
Affiliate placeholder {{AFF_TOOLNAME}} — referral link not configured.