How to Set Up MCP Servers in Claude Desktop on Mac (2026 Guide)

To add an MCP server to Claude Desktop on a Mac, install it as a desktop extension from Settings, or add it by hand to ~/Library/Application Support/Claude/claude_desktop_config.json and restart the app. Remote servers with a URL go in Customize > Connectors instead.

MCP (Model Context Protocol) servers give Claude tools, such as reading files or querying an app. This guide walks through each route on macOS, shows a minimal config that works, and explains how to check it loaded.

Checked against: the MCP project's local server guide, Anthropic's desktop extensions article and Anthropic's custom connector article on 2 November 2026.

What you need

• Claude Desktop for macOS from the download page. If it is already installed, use the Claude menu > Check for Updates....
• Node.js for servers that start with npx. Run node --version in Terminal. The MCP guide recommends the LTS release from nodejs.org.
• A server to add. Our MCP server finder helps you pick one.

Option 1: Install a desktop extension

1. Open Claude's Settings, then Desktop app, and select Manage next to Extensions. Older layouts show Settings > Extensions.
2. Click Browse extensions.
3. Choose an extension and click Install.
4. Enter any required settings, such as an API key.

For a .mcpb file from a vendor, click Advanced settings, find Extension Developer and choose Install Extension.... Anthropic says fields marked sensitive are kept in the Keychain on macOS. If macOS blocks something, Anthropic's article points to the Security & Privacy area of System Settings.

Option 2: Edit the config file

1. Click the Claude menu in the macOS menu bar and choose Settings.... This is the app's settings window, not your account settings.
2. Open the Developer tab and click Edit Config.
3. Add a server block, save, and quit Claude with Cmd+Q.
4. Reopen Claude.

Here is the macOS example from the MCP quickstart, which runs the official Filesystem server:

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

Replace username with your short user name (run whoami in Terminal if unsure). The quickstart explains that -y "automatically confirms the installation of the server package," and the folder paths are the only places the server may touch. Checked against the MCP quickstart on 2 November 2026.

To add a second server, add another entry inside mcpServers, separated by a comma. Our free MCP config generator writes valid blocks if you want to skip hand-editing.

Passing an API key

Most servers read keys from environment variables. Add an env object to the server entry:

{
  "mcpServers": {
    "brave-search": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-brave-search"],
      "env": {
        "BRAVE_API_KEY": "your-key-here"
      }
    }
  }
}

The file is plain text, so anyone with access to your Mac account can read the key. A desktop extension is the safer choice for secrets where one exists.

Option 3: Add a remote server

If the vendor gives you a URL, go to Customize > Connectors, click + Add and choose Add custom connector. Enter the name and URL, then sign in when prompted. Anthropic says custom connectors work on Free through Enterprise, with Free limited to one. These connectors also show up in Claude on the web, which local servers do not.

Verify the server loaded

After restarting, click the "Add files, connectors, and more" button at the bottom left of the message box. Hover over Connectors and click Manage connectors. Select your server to see its tools.

When Claude wants to use a tool, it asks for approval first. The MCP quickstart says "all actions require your explicit approval before execution."

Read the logs

If the server is missing, open Terminal and run:

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

The quickstart says mcp.log covers "general logging about MCP connections and connection failures," and mcp-server-SERVERNAME.log holds the server's stderr. Next, run the server command yourself to see its errors directly:

npx -y @modelcontextprotocol/server-filesystem /Users/username/Desktop

Common Mac mistakes

• npx not found by Claude. Apps launched from the Dock do not always see the PATH your shell sets, especially with Node version managers. Put the full path from which npx in command. Our macOS PATH fix covers this.
• Closing the window instead of quitting. Claude keeps running. Use Cmd+Q.
• Relative paths. The quickstart says folder paths must be absolute.
• Broken JSON. One trailing comma stops every server in the file from loading.
• Expecting local servers in Cowork or on the web. Anthropic says servers in this file "aren't available in Cowork or claude.ai."

Keep it safe

A local server runs with your macOS user's permissions. Grant only the folders a task needs, and read what a server does before installing it. Our MCP server risk checklist is a quick pre-install review.

Next step

Once your first server works, connect a business app. Our Claude connect guides cover Notion, Slack, HubSpot and more, such as connecting Claude to Notion. If developers on your team need servers shared through a repository, see the Claude Code mcp add guide.

Frequently asked questions