Claude MCP: Connect MCP Servers to the Claude App

Claude MCP explained: add remote MCP servers as custom connectors, install desktop extensions, and edit claude_desktop_config.json in Claude Desktop.

Josh Pocock8 min read

Claude MCP cover

AI Coding

Claude MCP

Stride AI Academy

Claude MCP means connecting Claude to MCP servers, the Model Context Protocol programs that give Claude access to outside tools and data. In the Claude apps you can pick a ready-made connector from the Connectors Directory, add a remote MCP server as a custom connector, install a desktop extension in Claude Desktop, or list a local server in Claude Desktop's claude_desktop_config.json file. Custom connectors work on every plan, including Free, which is limited to one.

This guide covers what MCP is, each way to connect a server to claude.ai and Claude Desktop, the config file, how to turn connectors on in a chat, and the safety checks worth doing. If you want MCP in Claude Code instead, that's a different setup: see how to add an MCP server to Claude Code. Everything here was checked against the Help Center articles on custom connectors using remote MCP, the Connectors Directory and local MCP servers on Claude Desktop, and the MCP project's guide to connecting local servers, on November 22, 2026.

What is Claude MCP?

MCP is an open protocol. The MCP docs describe MCP servers as programs that "extend AI applications' capabilities by providing secure, controlled access to local resources and tools." Each server exposes tools, and Claude can call them, with your approval, to read files, search a database, create a ticket or whatever else the server offers.

There are two kinds of server, and they connect differently:

Remote MCP server Local MCP server
Where it runs On the internet On your computer
How you add it Custom connector (or a Directory connector) Desktop extension or claude_desktop_config.json
Works in claude.ai, Claude Desktop, Cowork, mobile Claude Desktop only (and a locally running Cowork session)
Who connects to it Anthropic's cloud Your machine

The Help Center is clear on the split: local servers in claude_desktop_config.json use your local network and aren't available in claude.ai or cloud Cowork sessions.

Option 1: use a connector from the Connectors Directory

Before building anything, check whether the service already has a connector. The Connectors Directory lists pre-built ones, each with a page showing what it can read or write.

To open it:

  1. In a chat, click the + button in the lower left (or type /), hover over Connectors and select Manage connectors.
  2. Click the + next to Connectors.

Or go to Customize > Connectors and click the + there. Pick a connector, review what it does, and connect. Some carry an Interactive badge, meaning they can show live interfaces such as dashboards inside the conversation.

Option 2: add a remote MCP server as a custom connector

If the service isn't in the directory but has a remote MCP server URL, add it yourself. The Help Center says custom connectors work on Claude, Cowork and Claude Desktop for Free, Pro, Max, Ultra, Team and Enterprise plans. Free users can add one.

On Pro and Max (and Free, for one connector)

  1. Go to Customize > Connectors.
  2. Click + Add, then Add custom connector.
  3. Enter a name.
  4. Enter the server URL exactly as the provider documents it, including any path, then click Continue.
  5. Review the detected sign-in settings, then click Continue.
  6. Under Authentication, choose Sign in now, Sign in when needed or No sign in.
  7. Choose an OAuth client option. Use Claude's published identity is the recommended one.
  8. Add request headers if the server needs a fixed API key or bearer token.
  9. Click Add.

If the server's docs say you must use your own OAuth client, choose Use your own OAuth client, enter its Client ID and Client Secret, and register https://claude.ai/api/mcp/auth_callback as the redirect URL.

On Team and Enterprise

Only Owners and Primary Owners can add custom connectors for the organization, plus people with a custom role that includes Manage access to Libraries on Enterprise. They go to Organization settings > Connectors, click Add, hover over Custom and select Web, then fill in the same fields. Members then find it under Customize > Connectors and click Connect. Adding a connector doesn't give anyone access on its own: each person signs in individually.

Why a remote server won't connect

This trips people up. From the Help Center:

  • Claude connects from Anthropic's cloud, not your device. That's true on every client, including mobile.
  • The server must be on the public internet. Servers behind a VPN, on a private network or behind a firewall won't connect, even if you can reach them yourself.
  • Use port 443. A URL with another port, such as :8443, won't work.
  • Private servers need an allowlist. Add Anthropic's published IP ranges to your firewall.

To change a connector's details later, remove it and add it again.

Option 3: install a desktop extension in Claude Desktop

Desktop extensions are the easy way to run a local MCP server. The Help Center describes them as single-click installable packages, so you don't edit JSON or install dependencies by hand. Claude Desktop includes its own Node.js, and extensions can be Node.js, Python or binary servers.

To install one from the directory:

  1. Go to Settings > Desktop app and select Manage next to Extensions. In the older layout, it's Settings > Extensions.
  2. Click Browse extensions, then Install on the one you want.
  3. Fill in any settings it asks for, such as an API key.

To install a custom extension from a .mcpb file, open the same Extensions page, click Advanced settings, find Extension Developer and click Install Extension.

Option 4: edit claude_desktop_config.json

The manual route is the Claude Desktop config file. It's for servers that don't ship as an extension, or when you want full control over the command.

Where the Claude Desktop MCP config lives

From the MCP project's guide:

System Path
macOS ~/Library/Application Support/Claude/claude_desktop_config.json
Windows %APPDATA%\Claude\claude_desktop_config.json
Linux ~/.config/Claude/claude_desktop_config.json

To open it, click the Claude menu in your system's menu bar (not the settings inside the Claude window), choose Settings, open the Developer tab and click Edit Config. That creates the file if it doesn't exist.

A Claude MCP config example

This is the MCP guide's example for the Filesystem server on Windows. It gives Claude access to two folders:

JSON
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "C:\\Users\\username\\Desktop",
        "C:\\Users\\username\\Downloads"
      ]
    }
  }
}

On macOS, use paths like /Users/username/Desktop. Each key under mcpServers is a server name, command is what starts it and args are its arguments. This route needs Node.js installed for npx, and the guide says to use absolute paths. The server runs with your user account's permissions, so only list folders you're happy for Claude to read and change.

Save the file, then fully quit and restart Claude Desktop. To check it worked, click the + in the chat box, hover over Connectors and choose Manage connectors, then select the server to see its tools.

When a local server doesn't show up

The MCP guide's checklist:

  1. Restart Claude Desktop completely.
  2. Check the JSON syntax.
  3. Make sure every path is absolute.
  4. Read the logs. On macOS they're in ~/Library/Logs/Claude, on Windows in %APPDATA%\Claude\logs. mcp.log covers connections, and mcp-server-SERVERNAME.log holds each server's output.
  5. Run the server's command in a terminal to see its errors.

How to turn a connector on in a chat

Connected servers aren't always on. Per conversation:

  1. Click the + button in the lower left of the chat box (or type /).
  2. Hover over Connectors.
  3. Toggle on the ones you want for this chat.

On mobile, the Help Center says installing connectors is in beta, and services you connect on the web or desktop show up on mobile the next time you log in.

Stay safe with MCP servers

An MCP server can read your data and take actions, so the Help Center's advice is worth following:

  • Only connect servers from people you trust. Anthropic hasn't verified custom connectors.
  • Review the permissions asked for at sign-in and deny ones you don't need.
  • Watch for prompt injection. A malicious server can hide instructions in its tool output.
  • Use "Allow always" sparingly, only for tools you'd let run unsupervised.
  • Turn off tools you don't need in a conversation from the Search and tools menu.
  • On Team plans, a fixed credential is shared by every user, so use one with limited access.

Claude MCP vs MCP in Claude Code

Claude Code has its own commands and files for adding MCP servers. If you code with Claude Code, follow how to add an MCP server to Claude Code, and see the best MCP servers for Claude Code for ones worth installing. Want to make your own? Our guide to building an MCP server starts from scratch.

Learn to build with Claude Code

The Stride AI Coding course teaches Claude Code and Codex for building client tools, written for non-programmers, with weekly live calls to review your builds. Many of the free guides cover Claude Code setups, and the Claude Code community is where members compare theirs.

FAQ

What is Claude MCP?

It's Claude's support for the Model Context Protocol, an open standard for connecting AI apps to outside tools and data. In the Claude apps you add MCP servers as custom connectors, desktop extensions or entries in Claude Desktop's config file.

Can I use MCP on the free Claude plan?

Yes. Custom connectors using remote MCP are available on Free, Pro, Max, Ultra, Team and Enterprise. Free users are limited to one custom connector.

Where is the Claude Desktop MCP config file?

On macOS it's ~/Library/Application Support/Claude/claude_desktop_config.json, on Windows %APPDATA%\Claude\claude_desktop_config.json. Open it from the Claude menu: Settings, the Developer tab, then Edit Config.

Why won't my remote MCP server connect to Claude?

Claude connects from Anthropic's cloud, so the server must be reachable on the public internet over port 443. Servers behind a VPN, on a private network or behind a firewall won't connect unless you allowlist Anthropic's IP ranges.

Do local MCP servers work on claude.ai?

No. Local servers in claude_desktop_config.json run on your machine and only work in Claude Desktop and locally running Cowork sessions. For claude.ai and mobile, use a remote server as a custom connector.

Is MCP in Claude Desktop the same as in Claude Code?

Not quite. Claude Desktop uses connectors, extensions and claude_desktop_config.json, while Claude Code has its own commands and files for adding servers, covered in our Claude Code MCP guide.

Build it with us in Stride AI Academy

Four courses, weekly live calls and a community of people building and selling AI. Or start with 320+ free guides.

Keep reading

Free AI Coding guides