# How to add an MCP server to Claude Desktop

Level 3: Connect AI to your tools · 8 min · Updated 19 November 2026 · Path: Connect MCP servers to your assistant

By the end you'll add a remote or a local MCP server to Claude Desktop and check that Claude can see its tools.

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](https://ai-powered.com/academy/glossary/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](https://ai-powered.com/academy/glossary/remote-vs-local-mcp-server) explains the difference.

*Diagram: Local and remote MCP servers.* A local server runs on your computer and talks to the app over stdio. A remote server runs on the internet; the app reaches it by https URL, usually after you sign in.

## 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.

**Steps**

1. Go to **Customize** → **Connectors**.
2. Choose **+ Add**, then **Add custom connector**.
3. Enter a name and the server's full URL, including any path (for example `https://mcp.example.com/mcp`). Choose **Continue**.
4. Check the sign-in Claude detected and pick **Sign in now**, **Sign in when needed** or **No sign in**.
5. If the server gave you an API key or token instead, add it under **Request headers**.
6. 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:

- [GitHub](https://ai-powered.com/mcp/github-2): Official MCP server connecting AI assistants to GitHub repos, issues and workflows (server URL: `https://api.githubcopilot.com/mcp/`)
- [Context7](https://ai-powered.com/mcp/context7): Version-specific library docs and code examples piped into coding agents via MCP (server URL: `https://mcp.context7.com/mcp`)
- [Solana MCP by Vybe](https://ai-powered.com/mcp/solana-mcp-by-vybe): Remote MCP server exposing the Vybe Solana API to AI clients and code editors (server URL: `https://mcp.vybenetwork.xyz`)
- [SSRS2](https://ai-powered.com/mcp/ssrs2): Check, edit and preview RDLC reports, and turn Markdown into Word, PowerPoint or PDF (server URL: `https://ssrs2.net/mcp`)

## 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.

**Steps**

1. Open the **Claude** menu in your computer's menu bar (not the settings inside the chat window) and choose **Settings…**.
2. Open the **Developer** tab and choose **Edit Config**. Claude creates the file if it doesn't exist yet.
3. Add your server inside `mcpServers`: a name you choose, the `command`, its `args`, and `env` for any keys.
4. 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](https://ai-powered.com/mcp/playwright-mcp-2) in Claude Desktop (claude_desktop_config.json):

```json
{
  "mcpServers": {
    "playwright-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@playwright/mcp"
      ]
    }
  }
}
```

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.

**Try it**

Ask for something small that needs the server. With Playwright: "Open example.com and tell me the page title." Claude will ask before it runs the [tool call](https://ai-powered.com/academy/glossary/tool-call). Read what it wants to do, then allow it.

## 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/Claude` on macOS, `%APPDATA%\Claude\logs` on Windows. `mcp.log` covers connections; `mcp-server-<name>.log` holds each server's own output.

**Before you add any server**

A local server runs with your account's permissions: it can read and change anything you can. A connector acts with your permissions in the service it connects to. Anthropic notes that custom connectors aren't verified by Anthropic and that a malicious server can hide instructions in what it returns. Add servers you trust, give a file server only the folders it needs, and switch off tools you don't use.

## Key takeaways

- 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

- Add the same server to [Claude Code](https://ai-powered.com/academy/connect-mcp-servers/claude-code) with a single command.
- Browse [MCP servers](https://ai-powered.com/mcp) 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?](https://ai-powered.com/academy/glossary/tool-call)

## Sources

Official documentation, checked on 19 November 2026:

- [Getting started with custom connectors using remote MCP (Claude Help Center)](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp)
- [Connect to local MCP servers (modelcontextprotocol.io)](https://modelcontextprotocol.io/docs/develop/connect-local-servers)

Next lesson: [How to add an MCP server to Claude Code](https://ai-powered.com/academy/connect-mcp-servers/claude-code)
