MCP client setup: Claude, Cursor, ChatGPT and the rest
An MCP client is the application on the other end of the protocol: the AI app that discovers a server's tools and decides when to call them. The server does the work; the client decides what the model is even allowed to see.
The differences between clients matter more than most people expect. Claude Desktop and Cursor run local stdio servers directly. ChatGPT connects to remote HTTP endpoints only, which quietly rules out most of the ecosystem unless you bridge it. Some clients cap how many tools they will hold in context at once — which is why the fifth server you add can make the agent worse, not better.
The guides below cover setup per client, plus the tool-budget math that decides how many servers you can actually run before quality drops.
Pick your client first, then pick servers that match its transport support. Doing it the other way round is how people end up with a config that silently loads nothing.
25 articles · page 2 of 2
Claude Code MCP Config: Setup, Scopes & JSON
Where the config actually lives, the three scopes that trip people up, and the add commands that just work.
claude mcp add: Every Form of the Command
One CLI command wires any MCP server into Claude Code — here's every flag that matters and the ones you can ignore.
Cursor MCP Setup: mcp.json, OAuth & Fixes
The exact mcp.json, project vs global, OAuth remote servers, and the one-line fix for a server that connects but shows zero tools.
Claude Desktop MCP Configuration: The Exact Setup
One JSON file, one object, one hard restart — and four mistakes that eat an afternoon. Here's the exact Claude Desktop MCP configuration that works.
The Cursor tool-limit trap, and the math nobody does
The average MCP server exposes twelve tools. Cursor degrades past ~40. The wall is at four servers, not fifty — and almost no one does this arithmetic before they hit it.
FAQ
What is an MCP client?
An MCP client is the AI application that connects to MCP servers, discovers their tools, and calls them on the model's behalf. Claude Desktop, Claude Code, Cursor, Windsurf, VS Code and ChatGPT are all MCP clients. The server provides capability; the client controls what the model can see and do.
Do all MCP clients support the same servers?
No, and this trips people up. Transport support is the dividing line: Claude Desktop and Cursor run local stdio servers, while ChatGPT connects to remote HTTP endpoints only. A local-only server will not work in a remote-only client without a bridge such as mcp-remote.
How many MCP servers can one client handle?
Fewer than you would like. Tool-selection quality degrades as active tools pile up, and a typical server exposes around a dozen tools, so most setups start to suffer past roughly four servers. Enable what the task needs rather than everything you own.
Other topics
Looking for a server rather than an article? Best MCP servers by task