How to Install MCP Servers in Claude Desktop: A Complete 2026 Guide

If you've heard about Model Context Protocol (MCP) servers but feel stuck trying to set one up, this guide is for you. By the end, you'll have a working MCP server connected to Claude Desktop — in under 10 minutes.

We'll cover what MCP servers actually are, how to install your first one, the config file you'll need to edit, and how to troubleshoot the most common errors people hit on day one.

What is an MCP server (in 60 seconds) #

An MCP server is a small adapter program that lets Claude (or Cursor, or any MCP-compatible tool) talk to a real system. Want Claude to read your local files? Install the Filesystem MCP server. Want it to query a Postgres database? Install the Postgres server. Want it to manage GitHub issues? You guessed it — there's a GitHub MCP server.

Without MCP servers, Claude is just a chat. With them, Claude becomes an assistant that can actually do things in your real systems.

The protocol was open-sourced by Anthropic in late 2024 and has since exploded — there are now dozens of official and community-built servers covering everything from databases to design tools to your Spotify playlist.

What you need before starting #

Before you install any MCP server, make sure you have:

1. Claude Desktop installed — download from claude.ai/download. The free plan works.
2. Node.js 18 or higher — many MCP servers run via npx. Check with node -v in your terminal. If you don't have it, grab it from nodejs.org.
3. Optionally, Python with uv — some servers use uvx instead of npx. Install uv with pipx install uv or curl -LsSf https://astral.sh/uv/install.sh | sh.
4. A text editor — VS Code, Sublime, even TextEdit on Mac. You'll be editing one config file.

That's it. No accounts, no signups, no API keys (yet — some servers need them, but your first one won't).

Step 1: Find the Claude Desktop config file #

Claude Desktop stores its MCP server configuration in a single JSON file. Its location depends on your operating system:

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

Linux (Claude Desktop unofficial builds):

~/.config/Claude/claude_desktop_config.json

If the file doesn't exist yet, that's fine — you'll create it in the next step.

Step 2: Pick your first server #

For your first install, I strongly recommend the Filesystem server. Here's why:

• It's official (built by Anthropic)
• It needs zero API keys
• It works locally — no network setup
• It's instantly useful: Claude can read, write, and search files in folders you choose

Other great first-time options:

• Memory server — gives Claude long-term memory across conversations
• Fetch server — lets Claude grab and read any web page
• Time server — basic but a good "hello world"
• SQLite server — query a local SQLite database

For this guide, we'll use Filesystem.

Step 3: Edit the config file #

Open claude_desktop_config.json in your editor. If the file is empty or doesn't exist, paste this:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/yourname/Documents"
      ]
    }
  }
}

Important: replace /Users/yourname/Documents with the actual path to a folder you want Claude to access. On Windows, use double backslashes like C:\\Users\\yourname\\Documents.

If the file already has other servers in it, just add "filesystem": { ... } inside the existing mcpServers block. JSON is picky about commas — make sure there's a comma between server entries but not after the last one.

Step 4: Restart Claude Desktop #

This is the step everyone forgets. Fully quit and reopen Claude Desktop for it to load the new config. Just closing the window isn't enough on macOS — use Cmd + Q or right-click the dock icon → Quit.

Once Claude restarts, you should see a small hammer icon (🔨) or tools indicator at the bottom of the chat input. That means MCP servers are loaded.

Step 5: Test it #

Try asking Claude:

"Can you list the files in the folder I gave you access to?"

If everything worked, Claude will use the Filesystem server, list your files, and report back. You can also ask it to read a specific file, summarize its contents, or even create a new file.

🎉 Congratulations. You just installed your first MCP server.

Common errors and how to fix them #

"MCP server failed to start" #

Usually a JSON syntax error. Paste your config into jsonlint.com to check for missing commas or brackets.

"Command not found: npx" #

Node.js isn't installed or isn't in your PATH. Reinstall Node from nodejs.org and restart Claude Desktop.

Server loads but Claude says it can't access the folder #

The path in your config is wrong. On macOS, paths use forward slashes; on Windows, use double backslashes. Avoid spaces in folder names if you can.

No hammer/tools icon appears #

The config file is in the wrong location, or Claude wasn't restarted. Double-check the path for your OS, then fully quit and reopen Claude.

"uvx: command not found" #

Some servers (like Time or SQLite) use Python's uv package manager. Install it: curl -LsSf https://astral.sh/uv/install.sh | sh on macOS/Linux, or pip install uv if you have Python.

What to install next #

Once you've got Filesystem working, here are five servers worth installing in order:

1. Memory — Claude remembers things across sessions
2. Fetch — let Claude read web pages
3. GitHub — manage repos, issues, PRs (needs a GitHub token)
4. Postgres — if you have a database
5. Slack — read and post in your workspace

Each one expands what Claude can actually do. Browse the full directory to find servers for your specific stack.

A few honest tips #

Start with one server, not five. It's tempting to install ten servers at once. Don't. Each one adds complexity, and when something breaks you'll have no idea which one caused it. Add servers one at a time, restart Claude, test, then move to the next.

Read the README. Every MCP server's GitHub repo has a README that explains what it does and how to configure it. Most install issues are answered there. If you click through to a server page on this site, the GitHub link goes straight to the source.

Trust signals matter. Official servers (built by Anthropic, GitHub, Microsoft, HashiCorp, etc.) are generally safer to install than community servers, because community servers can run arbitrary code on your machine. Check the GitHub stars, the README, and the author before installing anything that needs your credentials.

Sandboxing matters. When a server asks for file access, give it the smallest folder that works. When it asks for an API key, generate a token with the minimum permissions. MCP servers run with your user privileges — treat them like any other CLI tool.

Next steps #

You now know how to install MCP servers. The real fun starts when you start chaining them together — give Claude access to your filesystem AND your database AND your GitHub, and it becomes a genuinely powerful assistant for your day-to-day work.

Browse the full directory to discover servers for your stack, and check back weekly — we add new ones as they get released. If there's a server we don't have listed yet, submit it here and we'll add it.

Happy building. 🔧