Add MCP servers to your client
Every MCP client stores servers a little differently: a command, a JSON file with a different key, or a settings screen that only takes a URL. Pick yours for where the configuration lives, what goes in it, and graded servers to start with.
- MCP servers for Claude Code
Claude Code adds MCP servers from the command line. One command for a local server, one for a remote one, and a scope flag that decides who else gets it.
- MCP servers for Cursor
Cursor reads MCP servers from an mcp.json file, either for every project or for one. Many listings here also have a one-click Add to Cursor link.
- MCP servers for VS Code
VS Code uses MCP servers in Copilot's agent mode. Its config file looks like other clients' but uses a servers key and a type for each server.
- MCP servers for Claude Desktop
Claude Desktop starts local MCP servers from a JSON config file. Remote servers are added as connectors in settings instead.
- MCP servers for ChatGPT
ChatGPT connects to MCP servers as connectors. It only takes remote servers, reached by URL, so local packages that run on your machine are not an option.
- MCP servers for Windsurf
Windsurf's Cascade agent reads MCP servers from one config file in your home folder, with the same mcpServers shape as most clients.
- MCP servers for GitHub Copilot
GitHub Copilot uses MCP servers in three places: agent mode in your editor, the coding agent that works on GitHub, and Copilot CLI. Each has its own setup.