MCP Servers for Claude Desktop — Complete Setup Guide (2026)

Last updated April 2026. Tested on Claude Desktop 0.9+ on macOS 15 Sequoia and Windows 11.

---

What MCP servers do in Claude Desktop

MCP servers give Claude access to external tools and real-world data. Without them, Claude can only work with what it learned during training and what you paste into the chat. With MCP servers, Claude can search the web, read live documentation, query databases, manage files, and interact with any service the server exposes.

Claude Desktop was one of the first applications to support MCP — Anthropic created the protocol — so its MCP support is mature and well-tested.

---

Method 1: One-command install (recommended)

The fastest way to add an MCP server to Claude Desktop:

bashCOPY
# Install the AgenticMarket CLI (once)
npm install -g agenticmarket

# Authenticate (once)
agenticmarket auth am_live_your_key

# Install any server — Claude Desktop gets configured automatically
agenticmarket install agenticmarket/duckduckgo

The CLI detects Claude Desktop, writes the correct config to your claude_desktop_config.json, and the server appears after a restart. No JSON editing needed.

---

Method 2: Extensions directory (GUI)

Claude Desktop now includes a built-in Extensions directory for installing MCP servers without touching config files:

1. Open Claude Desktop
2. Go to Settings → Extensions
3. Click "Browse extensions" to open the directory
4. Find the server you want and click Install
5. If the server requires credentials (like an API key), Claude prompts you to enter them securely

This is the simplest method for non-technical users, though the Extensions directory doesn't yet include all available MCP servers.

---

Method 3: Manual JSON setup

For custom servers or advanced configurations, edit the claude_desktop_config.json file directly.

Finding the config file

Via the app:

1. Open Claude Desktop
2. Click Claude menu (macOS) or Settings (Windows)
3. Go to Settings → Developer → Edit Config

Direct file paths:

Remote HTTP server

jsonCOPY
{
  "mcpServers": {
    "web-reader": {
      "url": "https://your-server-url/mcp"
    }
  }
}

Local stdio server

jsonCOPY
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
    }
  }
}

With environment variables (API keys)

jsonCOPY
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

Security note: Store sensitive tokens in the env block, not in args. The env block keeps credentials out of process listings. For production use, consider using a secrets manager or environment variable injector. Never commit API keys to source control.

---

The full-quit requirement

This catches almost everyone at least once:

Claude Desktop does not reload its config when you close the window. You must fully quit the application:

• macOS: Cmd+Q (not just closing the window — the app stays in the dock)
• Windows: Right-click the taskbar icon → Exit (not just clicking the X)

After quitting and reopening, wait a few seconds before testing. There's no visual confirmation that the config loaded — the only way to verify is to ask Claude something that requires the server.

I've personally spent 20 minutes debugging a "broken" config only to realize I hadn't actually restarted Claude Desktop. If your config looks correct but nothing works, quit fully and reopen first.

---

Verifying the server is active

Claude Desktop doesn't have a dedicated MCP settings panel like Cursor. To verify your server is working:

1. Open a new conversation
2. Ask Claude: "What tools do you have access to?"
3. Claude should list the tools from your configured servers
4. Test with a real task: "Use the [tool-name] tool to [specific action]"

If Claude says it doesn't have access to any tools, the config didn't load. Check the troubleshooting section below.

---

Recommended MCP servers for Claude Desktop

Browse all available servers at agenticmarket.dev/servers or explore community servers at agenticmarket.dev/explore.

---

Troubleshooting Claude Desktop MCP issues

Server doesn't appear after config change

• Did you fully quit Claude Desktop? Closing the window isn't enough. On Mac: Cmd+Q. On Windows: right-click taskbar → Exit
• Verify the JSON syntax — paste into jsonlint.com. One misplaced comma breaks everything
• Check the root key is mcpServers (not servers — that's for VS Code)

Claude says it has no tools

• The config file may be in the wrong location — verify the path from Settings → Developer → Edit Config
• If using stdio servers, the runtime (node, python) may not be on Claude Desktop's PATH — use absolute paths from which node

Server was working but stopped

• Check if Claude Desktop updated — protocol handling may have changed
• Re-verify by fully quitting and reopening
• Check the MCP logs for errors:

bashCOPY
# macOS — stream new entries
tail -f ~/Library/Logs/Claude/mcp*.log

# Windows — read the latest log
type %APPDATA%\Claude\logs\mcp*.log

Claude ignores tools for simple questions Claude sometimes declines to call external tools for queries it can answer from training data. This is by design — it optimizes for efficiency. Give it a task that clearly requires live data: "Search the web for [specific current event]" or "Read the content at [URL]".

Still stuck? See our complete MCP troubleshooting guide for every error code and fix, or validate your endpoint in the MCP Playground.

---

Next steps

• MCP Servers for VS Code — Setup Guide — if you also use VS Code
• MCP Servers for Cursor — Setup Guide — for Cursor users
• MCP Servers for Windsurf — Setup Guide — for Windsurf users
• What is MCP? — understand the protocol from the ground up
• How to Install MCP Servers Without JSON — full multi-IDE guide
• MCP Server Not Working? — troubleshooting every error

---

This guide is updated when Claude Desktop changes its MCP handling. Last reviewed April 2026 on Claude Desktop 0.9+.