Skip to content
Cognova AI

AI Tools & ReviewsHow-to guide

How to Connect an MCP Server to Claude (App, Desktop, Code)

By , AI consultantsPublished

In short

How you connect an MCP server to Claude depends on where the server runs. For a server with a public HTTPS URL, add it in the Claude app under Customize > Connectors > Add custom connector. For a server that runs on your own computer, install it as a Claude Desktop extension or add it to claude_desktop_config.json and restart the app. In Claude Code, use claude mcp add --transport http <name> <url>, or claude mcp add <name> -- <command> for a local server. Connect only servers you trust.

MCP, the Model Context Protocol, is the standard way to connect Claude to other software, such as a CRM, a project tracker or your company's own database. "Claude mcp" is searched about 5,400 times a month in the US, according to Semrush, but most top results cover one product's server rather than how Claude itself handles MCP.

This guide covers the three places you can connect a server: the Claude app, Claude Desktop and Claude Code. It follows Anthropic's and the MCP project's documentation as published on November 20, 2026. It is for business owners weighing integrations and for the technical person who will set them up. We checked the Claude Code commands on our own Windows 11 PC.

What you need

  • A Claude account (Free allows one custom connector) or Claude Code
  • The MCP server's details: a public HTTPS URL for remote servers, or the install command for local servers
  • Node.js, if a local server is started with npx
  • Admin rights in your Claude organization, if you are adding a connector for a Team or Enterprise plan

Time needed

10–30 minutes per server

  1. Step 1: Work out which kind of server you have

    A remote server has a web address and runs on the provider's infrastructure; you add it as a custom connector, and it works in the Claude app on any device. A local server runs on your own computer; you add it to Claude Desktop or Claude Code. Anthropic notes that remote connectors are reached from Anthropic's cloud, so the server must be public over HTTPS on port 443.

  2. Step 2: Add a remote server as a custom connector

    In the Claude app, go to Customize > Connectors, click + Add, then Add custom connector. Enter a name and the server URL exactly as the provider documents it, click Continue, then Add, and sign in if the server asks. Anthropic says this works on Free, Pro, Max, Ultra, Team and Enterprise, but Free accounts are limited to one custom connector.

  3. Step 3: Add a connector for your whole team

    On Team plans only Owners and Primary Owners can add custom connectors, and on Enterprise also people whose custom role allows it. Go to Organization settings > Connectors, click Add, hover over Custom, choose Web, enter the name and URL, and click Continue. Choose how members authenticate, then click Add. Members then open Customize > Connectors, click Connect and sign in with their own account.

  4. Step 4: Install a local server as a Desktop extension

    Many local servers ship as Claude Desktop extensions, which are single .mcpb files. In Claude Desktop, open Settings > Desktop app and click Manage next to Extensions (older versions show Settings > Extensions), then Browse extensions and Install. To install an extension file a provider sent you, drag the .mcpb file onto the Extensions page. Anthropic says an extension can access only what you can access on your computer.

  5. Step 5: Or add a local server to the config file

    For servers that are not packaged as extensions, edit claude_desktop_config.json. It is at %APPDATA%\Claude\claude_desktop_config.json on Windows and ~/Library/Application Support/Claude/claude_desktop_config.json on macOS. Add the server under mcpServers as shown in the example below, save, then quit Claude Desktop completely and reopen it. Local servers added this way are not available on claude.ai or in Cowork tasks that run in the cloud.

  6. Step 6: Add a server in Claude Code

    For a remote server, run claude mcp add --transport http notion https://mcp.notion.com/mcp, replacing the name and URL. For a local server, put the start command after --, for example claude mcp add my-server -- npx my-mcp-server, and pass keys with -e KEY=value rather than typing them into files you share. Add --scope user to use a server in all projects or --scope project to share it through a .mcp.json file.

  7. Step 7: Check the connection and sign in

    In Claude Code, run claude mcp list to see each server's status, such as Connected, Needs authentication or Failed to connect, and type /mcp inside a session to sign in to servers that use OAuth. In Claude Desktop, open the + menu in the message box, choose Connectors and check the server is listed and switched on. If a local server fails, read its log in %APPDATA%\Claude\logs on Windows or ~/Library/Logs/Claude on macOS.

  8. Step 8: Limit what each server can do

    Connect only servers from organizations you trust. Anthropic warns that servers which fetch outside content can expose you to prompt injection, where hidden instructions try to redirect Claude. Give a local file server access only to folders you are comfortable with Claude reading and changing, use Always ask for tools that change data, and choose Always allow only for trusted servers.

Example: a local file server in Claude Desktop

This is the filesystem example from the MCP project’s documentation for Windows. Replace username with your Windows user name, and list only the folders you want Claude to reach:

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

On macOS, the folder paths look like /Users/username/Desktop. Backslashes in Windows paths must be doubled inside JSON. The server runs with your own user account’s permissions.

Claude Code scopes

Scope Where it works Where it is saved
local (default) Only the current project, only for you ~/.claude.json
project The current project, for everyone who uses it .mcp.json in the project folder
user All your projects ~/.claude.json

Claude Code asks for approval before it loads servers from a project’s .mcp.json file, so a teammate cannot silently add one.

Transports in plain terms

Anthropic’s Claude Code docs call HTTP (also known as Streamable HTTP) the recommended transport for remote servers. The older SSE transport is deprecated, though still supported with --transport sse. Local servers use stdio, which simply means Claude starts the program and talks to it directly.

What we verified

On a Windows 11 PC with Claude Code 2.1.312, we checked claude mcp --help and claude mcp add --help on November 20, 2026. This confirmed the add, add-json and get commands, the --transport option (stdio, sse, http), -e/--env for environment variables, and -s/--scope with local, user and project. We did not add a connector to a Claude app account or edit a Claude Desktop config for this guide; those steps come from Anthropic’s and the MCP project’s documentation.

How Cognova AI can help

We connect Claude, chatbots and voice agents to the systems small businesses already use, including CRMs, calendars and document stores, and build custom MCP servers where none exists. See AI Chatbot Development, AI Consulting or our guide to creating Claude skills.

Frequently asked questions

What is an MCP server?

An MCP server is a small program that exposes another system's data and actions, such as searching a CRM or creating a calendar event, in the Model Context Protocol format. Claude, ChatGPT and many other AI tools can connect to MCP servers, so one server can serve several assistants. Some servers are hosted by the software vendor, and others run on your own computer.

Can I use MCP servers on the free Claude plan?

Yes, with a limit. Anthropic's help center says Free users can add one custom connector, which is a remote MCP server reached by URL. Pro, Max, Ultra, Team and Enterprise plans can add more. Local servers in Claude Desktop and servers in Claude Code are configured separately from that connector limit, though Claude Code itself needs a paid plan or API account.

Why does my local MCP server not show up in Claude Desktop?

The most common causes are a JSON syntax error in claude_desktop_config.json, not fully quitting and reopening Claude Desktop, or a missing program such as Node.js for servers started with npx. On Windows, the MCP docs also mention an ENOENT error that is fixed by adding the APPDATA path to the server's env settings. Check the mcp log files in the Claude logs folder for the exact error.

Sources

  1. 1Anthropic: Connect Claude Code to tools via MCP
  2. 2Anthropic: Add an unlisted connector
  3. 3Anthropic Help Center: Get started with custom connectors using remote MCP
  4. 4Anthropic Help Center: Get started with local MCP servers on Claude Desktop
  5. 5Model Context Protocol: Connect to local MCP servers
  6. 6MCP Bundles (mcpb) on GitHub
  7. 7Semrush Keyword Overview: claude mcp (US database, November 2026)

Cite this article

Cognova AI. (2026, November 20). How to Connect an MCP Server to Claude (App, Desktop, Code). Cognova AI. https://cognovaai.com/insights/how-to-connect-mcp-server-to-claude

Permanent link: cognovaai.com/insights/how-to-connect-mcp-server-to-claude. Quoting a passage? Select it and use “Copy quote” to get a link that jumps to that exact text.

Up nextHow to Create Claude Skills for Claude and Claude Code (2026)A Claude skill is a folder with a SKILL.md file: a short YAML header with a name and a description, followed by plain-language instructions. In Claude Code, save it as ~/.claude/skills/<skill-name>/SKILL.md for yourself or .claude/skills/<skill-name>/SKILL.md in a project, and run it with /skill-name or let Claude load it when a request matches. In the Claude app, turn on code execution, zip the folder and upload it under Customize > Skills.Continue reading

See where AI fits in your business

A 30-minute call with a consultant, not a sales rep. You leave with at least one concrete next step, whether or not we work together.