You ask Claude about last week's bug reports, and it says, politely, that it can't see your issue tracker. So you copy, paste, copy, paste. An MCP server ends that: it gives Claude a direct, approved line into a tool you use, and Claude can then look things up and take small actions for you.
Claude Desktop accepts two kinds of server, and they live in different places:
- A remote server is a URL on the internet. You add it as a custom connector. Anthropic documents connectors for Claude on the web and Cowork too.
- A local server is a program on your own computer. You add it to a config file that only Claude Desktop reads.
Not sure which one you have? If the server's page gives you a URL, it's remote. Remote vs local MCP servers explains the difference.
Add a remote server as a connector
As of 19 November 2026, Anthropic's help center says custom connectors work on the Free, Pro, Max, Ultra, Team and Enterprise plans. Free accounts can add one.
- Go to Customize → Connectors.
- Choose + Add, then Add custom connector.
- Enter a name and the server's full URL, including any path (for example
https://mcp.example.com/mcp). Choose Continue. - Check the sign-in Claude detected and pick Sign in now, Sign in when needed or No sign in.
- If the server gave you an API key or token instead, add it under Request headers.
- Choose Add.
On Team and Enterprise, an owner adds the connector once under Organization settings → Connectors (Add → Custom → Web). Everyone else then connects to it from Customize → Connectors.
To use it, open the + menu at the bottom left of a chat, choose Connectors and switch it on for that conversation.
One thing catches people out: Claude calls remote servers from Anthropic's cloud, not from your laptop. The server has to be reachable on the public internet and use the normal HTTPS port, 443, so a server on your office network won't work as a connector.
Want something to try? These hosted servers answered our most recent check, so they're reachable by URL right now:
Hosted MCP servers for developer tools that answered our latest check, most popular first. Copy a server URL to add it.
More for developer tools
GitHub
Official MCP server connecting AI assistants to GitHub repos, issues and workflows
https://api.githubcopilot.com/mcp/Answered our last check on 19 November 2026

Context7
Version-specific library docs and code examples piped into coding agents via MCP
https://mcp.context7.com/mcpAnswered our last check on 19 November 2026

Solana MCP by Vybe
Remote MCP server exposing the Vybe Solana API to AI clients and code editors
https://mcp.vybenetwork.xyzAnswered our last check on 19 November 2026

SSRS2
Check, edit and preview RDLC reports, and turn Markdown into Word, PowerPoint or PDF
https://ssrs2.net/mcpAnswered our last check on 19 November 2026
Add a local server in the config file
Local servers need whatever starts them, usually Node.js (for npx) or Python with uv (for uvx). Type node --version in a terminal; if you see a version number, you're set.
- Open the Claude menu in your computer's menu bar (not the settings inside the chat window) and choose Settings….
- Open the Developer tab and choose Edit Config. Claude creates the file if it doesn't exist yet.
- Add your server inside
mcpServers: a name you choose, thecommand, itsargs, andenvfor any keys. - Save, quit Claude Desktop completely and open it again. It only reads the file when it starts.
The file lives here:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Here's a real example: Microsoft's Playwright server, which lets Claude open and click through web pages. This is the exact entry, built from its registry record:
Playwright MCP in Claude Desktop. Add to claude_desktop_config.json:
{
"mcpServers": {
"playwright-mcp": {
"command": "npx",
"args": [
"-y",
"@playwright/mcp"
]
}
}
}Built from the server's registry entry, the same config as on its listing page.
If the file already has servers, add the new name inside the same mcpServers object. Two mcpServers blocks in one file won't work.
Check that it worked
Open the + menu ("Add files, connectors, and more"), point to Connectors and choose Manage connectors. Select your server to see its tools.
If the server doesn't show up
- Quit Claude Desktop properly (not just the window) and reopen it.
- Check the JSON. One missing comma stops the whole file loading.
- Use full paths in
args, not~or relative paths. - Run the command in a terminal, for example
npx -y @modelcontextprotocol/server-filesystem /Users/you/Desktop, and read its error. - Read the logs:
~/Library/Logs/Claudeon macOS,%APPDATA%\Claude\logson Windows.mcp.logcovers connections;mcp-server-<name>.logholds each server's own output.
In short
- Remote server (a URL): Customize → Connectors → Add custom connector.
- Local server (a command): Settings… → Developer → Edit Config, then restart.
- Check under + → Connectors → Manage connectors, and approve the first tool call by hand.
What to try next
Share this lesson- Add the same server to Claude Code with a single command.
- Browse MCP servers for the tools you use every day, and check each page's "runs locally" or hosted label.
- Learn what happens behind each approval in what is a tool call?