Almost every serious AI client supports the Model Context Protocol in 2026, but “supports MCP” covers a wide range. Claude Desktop runs MCP servers like it invented them, which it did. ChatGPT runs them too, behind a setting most people never find, on plans most people do not have.
So the useful answer is a tier list rather than a yes or no. Depth of support, cost and the small print vary a lot from one client to the next.
- First-class support: Claude Desktop and Claude Code. Built by the team that invented the protocol.
- Strong native support: Cursor, Devin Desktop (formerly Windsurf), VS Code with GitHub Copilot. MCP is a core feature, not an add-on.
- Behind a toggle or paid plan: ChatGPT (Developer Mode), Zed, Cline, Continue, LibreChat, Cherry Studio.
- Newer or narrower support: Gemini CLI, Microsoft Copilot Studio, Perplexity. This list changes fast.
- Same server, every client: wire one MCP endpoint and reuse it in every supported tool. Every ContextBolt product ships as one: Context Board, Bookmarks and SEO.
What does MCP support mean?
The Model Context Protocol is an open standard released by Anthropic in November 2024. It splits the job in two. The MCP server is the data source, a process or remote URL that exposes tools the AI can call. The MCP client, also called the host, is the AI tool you type into.
So “does this tool support MCP” means “can it act as an MCP client.” The same server then works in every supported client without changes: a GitHub server, a Postgres server, a Vercel MCP server, or a bookmark search server like ContextBolt. For how the protocol itself works, see What is MCP?.
Clients support different slices of it. Some take remote HTTP servers but not local stdio ones, some only read tools, some use OAuth and some only API keys. The tiers below sort by that depth.
Tier 1: First-class MCP support
MCP is a primary design feature in these two. The integration is the deepest, the docs are the cleanest, and the bug rate is the lowest.
Claude Desktop
The original MCP client, with three install paths. Custom Connectors in the UI handle remote servers, .mcpb Desktop Extensions give one-click local installs, and the raw claude_desktop_config.json file gives full control. It supports local stdio servers, remote HTTP servers and OAuth-authenticated cloud servers, on macOS and Windows.
Add remote servers under Customize, then Connectors, then the + button, then Add custom connector. They do not go in claude_desktop_config.json, which is for local servers. Custom connectors work on Pro, Max, Team and Enterprise, and free plans can add one. On Team and Enterprise an Owner adds it under Organization settings, then Connectors.
If your AI work is conversational and you do not live in an IDE, this is the right home. The setup guide is Claude Desktop MCP: Setup, Servers, and the 2026 Stack.
Claude Code
The terminal version. Claude Code reads .mcp.json from the project root and treats every server in it as a tool the agent can call. Project-level servers live in .mcp.json and are committed to git, user-level ones live in ~/.claude.json, and remote HTTP servers are added with claude mcp add --transport http <name> <url>.
The support matches Claude Desktop but is tuned for coding. Same servers, different config file. It needs a paid Claude plan or an Anthropic Console account.
Tier 2: Strong native support
These clients shipped support early, kept up with the spec, and treat it as a normal feature. Day to day, the experience is close to Tier 1.
Cursor
Cursor added MCP in early 2025. Config lives in ~/.cursor/mcp.json for user-level servers and .cursor/mcp.json for project-level ones. It supports stdio, SSE and HTTP servers, and the agent reads the available tools at the start of every Composer session. MCP is free on the Hobby plan. Setup guide: Cursor MCP integration.
Windsurf (now Devin Desktop)
Windsurf was renamed Devin Desktop on Jun 2, 2026, and Devin Local replaced Cascade as the main local agent. MCP shipped in early 2025. Devin’s docs put the config at ~/.config/devin/mcp_config.json on macOS and Linux and %APPDATA%\devin\mcp_config.json on Windows. It supports stdio, streamable HTTP and SSE, with OAuth for the HTTP and SSE transports. Keep the server count down, because with too many servers the agent starts thrashing. Setup details: Devin Desktop MCP setup.
VS Code with GitHub Copilot
MCP shipped to all VS Code users in v1.102 in July 2025, alongside Agent mode going generally available, per the Visual Studio team’s announcement. Since VS Code 1.146 (11 November 2026), new servers go in two files the Copilot harness reads: ~/.copilot/mcp-config.json for your own servers and .mcp.json at the project root for shared ones. The older .vscode/mcp.json and user profile file belong to the Local harness, which Microsoft deprecated in 1.146 and plans to remove in February 2027.
The main gotcha is the root key. The new files use mcpServers, like most other clients, while the old .vscode/mcp.json uses servers, so a block moved between them needs the key changed. Add servers with MCP: Add Server, or browse them from Chat: Open Customizations, and select Copilot in the Session Target dropdown. Detail: VS Code MCP: Setup, Servers, and the 2026 Stack.
Tier 3: Behind a toggle, a paid plan, or a beta
The protocol works in these. The friction is getting to it, whether that is a hidden setting, a paid plan, or both.
ChatGPT (Developer Mode)
OpenAI added full MCP support in 2025 under Developer Mode. Toggle it on at Settings, then Security and login, and you can add any compatible MCP server, not just the ones in OpenAI’s curated Apps panel.
It is paid plans only. OpenAI lists Plus, Pro, Business, Enterprise and Education, and it supports SSE and streaming HTTP servers. Write actions ask for your confirmation by default. Walkthrough: Make ChatGPT Remember Your Notes: 5 Methods (2026).
Zed
Zed added MCP in 2025 through its Assistant panel. Config lives in ~/.config/zed/settings.json under the context_servers key, which is Zed’s name for MCP servers. It supports the standard transports. It is lighter than Cursor or VS Code, and the Vim mode is the best in any AI-first editor.
Cline (and the forks)
Cline is the open-source coding agent that runs inside VS Code as an extension. It has full MCP support, configured through the Cline UI or a settings file. The forks (Roo Code, Kilo Code and others) inherit it from the parent codebase. Free, bring your own API key.
Continue
Continue is the other major open-source coding agent extension, for VS Code and JetBrains. MCP landed in 2025. Servers go in the mcpServers block of your Continue config (config.yaml) or as separate files in a .continue/mcpServers folder, and MCP only works in agent mode.
LibreChat
LibreChat is the most popular open-source ChatGPT-style web UI. It runs multiple models and added MCP server support in 2025, configured in YAML in the LibreChat config file. It suits teams that want a self-hosted multi-model chat with MCP without paying ChatGPT Team prices.
Cherry Studio
Cherry Studio is a desktop chat client for multiple model providers, with MCP built in. Configuration is UI-driven, which makes it the closest cousin to Claude Desktop for anyone who wants OpenAI, Anthropic and local models in one app.
Tier 4: Newer or narrower support
The list of holdouts has shrunk quickly. What remains is mostly about which product you mean.
- Google Gemini: Gemini CLI is a full MCP client, configured in
~/.gemini/settings.jsonor.gemini/settings.jsonwith stdio, SSE and streamable HTTP transports. - Microsoft Copilot: GitHub Copilot is covered above. Copilot Studio can connect an agent to an existing MCP server over streamable HTTP, but that is an agent builder, not a chat app you point at your own bookmarks.
- Perplexity: Paid plans can add custom remote MCP connectors under Account Settings, then Connectors. The feature is newer than most on this list.
Tools built by Anthropic and by the editor crowd shipped MCP early. General consumer AI apps came later, and most gate it behind paid plans.
MCP support compared
| Client | Local stdio | Remote HTTP | Free plan | Config location |
|---|---|---|---|---|
| Claude Desktop | Yes | Yes (Custom Connectors) | One custom connector | Connectors (remote), claude_desktop_config.json (local) |
| Claude Code | Yes | Yes | No (paid plan or Console) | .mcp.json (project) or user |
| Cursor | Yes | Yes (SSE / HTTP) | Yes | .cursor/mcp.json |
| Windsurf (Devin Desktop) | Yes | Yes | Yes | ~/.config/devin/mcp_config.json |
| VS Code (Copilot) | Yes | Yes | Yes (Copilot free tier) | ~/.copilot/mcp-config.json or .mcp.json (mcpServers key) |
| ChatGPT | No | Yes (Developer Mode) | No | Settings, Security and login |
| Zed | Yes | Yes | Yes | ~/.config/zed/settings.json |
| Cline / Continue | Yes | Yes | Yes (BYO key) | Extension settings, or config.yaml (Continue) |
ChatGPT is the only major client without local stdio servers, which makes sense, since you cannot run a process on OpenAI’s servers. And if you are not on a paid plan yet, the clients you can use with MCP shorten to about five.
Which MCP client should you pick?
Pick the client you would have used anyway, and check this list once to confirm it supports MCP. Changing your workflow to chase deeper MCP support is rarely worth it.
- A terminal: Claude Code. It is the best CLI agent on the market, and the MCP support is what you’d expect from the company that wrote the spec.
- Conversational work outside coding: Claude Desktop or ChatGPT. Claude Desktop has cleaner MCP wiring. ChatGPT has the larger Apps panel and the wider model spread. If you already pay for one, start there.
- An editor: your existing one is probably fine. Cursor and Devin Desktop suit AI-first workflows, and VS Code with Copilot covers everything else.
- Self-hosted, multi-model: LibreChat or Cherry Studio. Both keep your data local and both speak MCP. The trade-off is more setup and no managed updates.
Most people wire two or three servers, hit “tool overload” when the agent gets confused, and turn the rest off. So pick a small server stack first, then clients around it. A bookmark MCP, a GitHub MCP, a Postgres MCP and a filesystem MCP is a useful four-server starter in every client above. If you keep a knowledge vault, add an Obsidian server too; our Obsidian MCP setup guide walks through the options.
ContextBolt’s MCP servers
Free plans are still locked out of the deepest features: ChatGPT needs a paid plan for Developer Mode, and free Claude is limited to one custom connector. If you want a first server that fills itself, we build three, and each works from any client on this list.
ContextBolt Bookmarks is a Chrome extension that saves any web page with its text and captures your X, Reddit and LinkedIn saves as you make them. Basic is free and capped at 150 bookmarks, so the library can build while you decide. Pro ($6 a month) removes the cap and adds cloud sync and a personal MCP endpoint. Wire the endpoint into a client above and ask Claude what you saved about LLM evals last month, and it calls search_bookmarks against your collection. Start in Claude Code, switch to ChatGPT next year, and the bookmark layer follows you. The Claude Code setup is Add Your Bookmarks to Claude Code via MCP.
Context Board sits on both sides of the protocol. As a server, it lets any client above read and write your board, from pages and mind maps to tasks and live widgets. As a client, it signs in to remote MCP servers such as Stripe, Linear, Notion and Sentry and runs only their tools that read, to keep its widgets current. It is free for 3 days, then $12 a month.
ContextBolt SEO is a hosted MCP server for keyword research, difficulty scores, ranking data and AI visibility checks, with everything it returns saved to your SEO Dashboard. It starts with a 7-day free trial, then $35 a month. We put it next to the alternatives in Best SEO MCP Servers, and the SEO MCP overview covers what it returns.