Add MCP servers to Claude Desktop
Claude Desktop connects to MCP servers in two different ways. Remote servers are added as custom connectors in Settings; local servers are listed in a JSON configuration file that the app reads at startup. This guide covers both, using local examples adapted from this registry.
Remote servers: add a custom connector
Remote MCP servers are not added through the configuration file. Instead:
- Open Settings. On desktop, press
Ctrl+Commaor use the menu in the top-left corner. - Select Connectors in the sidebar.
- Choose Add, then Add custom connector, and enter the server URL, including
https://. - Complete the authentication the server asks for. Most remote servers use OAuth, which opens the provider's sign-in page in your browser.
After connecting, open the connector again in Settings to enable or disable individual tools. Turning off write tools you don't need is a simple way to reduce risk. Remote servers in this registry, with their URLs, include:
- Cloudflare Code Mode HTTP · OAuth authorization
- Cloudflare Docs HTTP · Not required
- GitHub MCP Server (remote) HTTP · GITHUB_PERSONAL_ACCESS_TOKEN
- Sentry HTTP · OAuth authorization
- Figma HTTP · OAuth authorization
- Context7 HTTP · Not required
- Exa HTTP · Not required
- Firecrawl HTTP · Not required
- Tavily HTTP · OAuth authorization
- Hugging Face HTTP · Not required
- Stripe HTTP · OAuth authorization
- Vercel HTTP · OAuth authorization
- AWS Knowledge HTTP · Not required
- Microsoft Learn HTTP · Not required
- Supabase HTTP · OAuth authorization
- Neon HTTP · OAuth authorization
- Linear HTTP · OAuth authorization
- Notion HTTP · OAuth authorization
- Atlassian Rovo HTTP · OAuth authorization
- Zapier HTTP · OAuth authorization
- AxisMCP for iPhone and iPad Streamable HTTP · AXISMCP_TOKEN
Connectors are part of your Claude account, so a connector added in the browser at claude.ai is also available in Claude Desktop. Availability can depend on your plan; check Anthropic's help pages if the option is missing.
Local servers: edit claude_desktop_config.json
Local servers run as programs on your computer, started by Claude Desktop. Open the configuration file from the app: go to Settings, choose the Developer tab and click Edit Config. The file is created if it doesn't exist. Its location is:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
The file holds an mcpServers object. Each entry has a command, its args and, if needed, an env object. That is the same shape as a local server in Cursor's mcp.json, so the registry's Cursor example for any local server can be used here. For example, the Filesystem server, with the folder Claude may access as its last argument:
claude_desktop_config.json.{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/REPLACE_WITH_ALLOWED_DIRECTORY"
]
}
}
}
Replace /REPLACE_WITH_ALLOWED_DIRECTORY with an absolute path. The official guide is explicit that relative paths do not work here. You can list more than one directory as extra arguments. A browser automation server that needs no settings looks like this:
claude_desktop_config.json.{
"mcpServers": {
"playwright-mcp": {
"command": "npx",
"args": [
"@playwright/mcp@latest"
]
}
}
}
Restart and confirm the server loaded
Claude Desktop reads the file only at startup, so quit the app completely and open it again after every change. Closing the window is not enough on macOS. When a server has loaded, its tools appear under the connectors control in the chat input, where you can manage them. Claude asks for your approval before it uses a tool, and shows the tool name and arguments, so you can see exactly what will happen before it runs.
Troubleshooting
- Check the JSON syntax. One misplaced comma stops all servers in the file from loading.
- Make sure every path is absolute.
- Run the server command yourself in a terminal. If
npxoruvxis missing, or a package name is wrong, the error appears straight away. - Read the logs. On macOS they are in
~/Library/Logs/Claude, and on Windows in%APPDATA%\Claude\logs.mcp.logcovers connections in general, andmcp-server-<name>.logholds the error output of each server.
tail -n 20 -f ~/Library/Logs/Claude/mcp*.log
Local servers that need credentials read them from the env object. Those values are stored in plain text in the configuration file, so use tokens with the narrowest permissions the server allows, or a remote server with OAuth where one exists.
Local servers that need credentials
Many local servers read an API key or connection string from their environment. In Claude Desktop you supply it in the entry's env object; the registry's examples mark each value you must fill in with REPLACE_WITH_.... The MongoDB example also starts the server with --readOnly, so the agent can query data but not change it:
claude_desktop_config.json.{
"mcpServers": {
"mongodb": {
"command": "npx",
"args": [
"-y",
"mongodb-mcp-server@latest",
"--readOnly"
],
"env": {
"MDB_MCP_CONNECTION_STRING": "REPLACE_WITH_MDB_MCP_CONNECTION_STRING"
}
}
}
}
On Windows, write paths inside JSON with doubled backslashes, for example C:\\Users\\you\\Documents, or use forward slashes. Each server you add starts as its own process when Claude Desktop opens, so remove entries you no longer use.
Using Claude Code as well?
Claude Code keeps its own server list, separate from Claude Desktop. To reuse an entry from claude_desktop_config.json, pass the inner JSON to claude mcp add-json, or follow the Claude Code and Codex guide. For the difference between connector-style remote servers and local processes, see remote vs local servers.
More setup guides
Sources
This guide was written from the official documentation below and last reviewed on 12 October 2026. Client interfaces change often; when a menu or file name here differs from what you see, the upstream documentation wins. Report a correction through the contact page.