Claude Desktop MCP Setup: A No-Code Guide (2026)

Out of the box, Claude Desktop can only see what you paste or upload. MCP (Model Context Protocol) lets it work with your folders, apps and services directly: read a project folder, search your notes, create a calendar event. You don’t need to write code. This guide shows the three ways to set it up, from easiest to most flexible, and how to fix the usual problems.

Checked against Anthropic’s help centre and the official MCP docs as of October 2026. Claude’s menus get renamed from time to time; if a label below doesn’t match exactly, look for the nearest equivalent.

Pick the right method

Method	Best for	Runs where	Effort
Connectors	Popular online apps (docs, chat, project tools)	Anthropic’s cloud	A few clicks + sign-in
Desktop extensions (.mcpb)	Local tools packaged for Claude	Your computer	One click
Config file	Any MCP server, including ones without an extension	Your computer	Paste some JSON

Start at the top and only move down when you need something the easier method can’t do.

Method 1: Connectors

Connectors work in Claude on the web, in Claude Desktop and on mobile.

1. In Claude, open Customize → Connectors (or from a chat: + → Connectors → Manage connectors).
2. Browse the directory and pick an app.
3. Click Connect and sign in to that app when asked.
4. In any chat, use + → Connectors to turn it on or off for that conversation.

On Team and Enterprise plans, an owner has to enable a connector for the organisation before members can connect their own accounts.

Custom connectors

If a service gives you an MCP server URL, add it under Customize → Connectors → + Add → Add custom connector: paste the name and URL, then choose how to sign in. Per Anthropic’s help centre, custom connectors are available on Free, Pro, Max, Team and Enterprise plans, with Free limited to one custom connector.

One catch: Claude reaches custom connectors from Anthropic’s cloud, even when you use the desktop app. A server running on localhost or behind your company VPN won’t work this way; use Method 2 or 3 instead.

Method 2: Desktop extensions (one click)

Desktop extensions are local MCP servers packaged as a single .mcpb file (older ones used .dxt). Claude Desktop has Node.js built in for them, so you don’t need to install anything else.

1. Open Claude Desktop Settings and find Extensions (in recent versions under Desktop app, then Manage).
2. Click Browse extensions, pick one, then Install.
3. Fill in any settings it asks for, such as an API key or which folder to allow. Fields marked sensitive are stored in your operating system’s keychain.

Got an .mcpb file from a developer? On the same Extensions page, open Advanced settings and use Install Extension… under Extension Developer.

Method 3: The config file

This works with any MCP server, including the many that don’t ship as extensions.

Step 1: Install Node.js (for most servers)

Many servers start with npx, which comes with Node.js. Install the current LTS version from nodejs.org, then check in a terminal:

node --version

Some servers require recent Node versions; for example, the current release of the official filesystem server declares Node 24 or later on npm. If a server fails to start, updating Node is the first thing to try.

Step 2: Open the config file

In Claude Desktop, open Settings from the Claude menu in your operating system’s menu bar (not the settings inside a chat), go to Developer, and click Edit Config. That creates the file if it’s missing and shows it in your file manager.

System	File location
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json

Step 3: Add a server

Here’s the official example that gives Claude access to your Desktop and Downloads folders, using the filesystem MCP server. Open the file in any text editor and paste:

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

Replace username with your own. On Windows, folders look like "C:\\Users\\username\\Desktop" (note the double backslashes). The folders you list are the only ones the server can reach, so keep the list short.

Servers that need a key take it in an env block:

{
  "mcpServers": {
    "my-service": {
      "command": "npx",
      "args": ["-y", "example-mcp-server"],
      "env": { "EXAMPLE_API_KEY": "paste-your-key-here" }
    }
  }
}

Adding a second server? Put it inside the same mcpServers block, separated by a comma. Don’t add a second mcpServers.

Step 4: Restart properly

Closing the window isn’t enough. Fully quit Claude Desktop: Cmd+Q on macOS, or right-click the tray icon and choose Quit on Windows. Then reopen it.

Step 5: Check it worked

Start a new chat, click + → Connectors, and look for your server. Then ask something that needs it: “List the PDFs in my Downloads folder.” Claude asks for permission before using a tool the first time.

Troubleshooting

Problem	Fix
Server doesn’t appear	Fully quit and reopen; check the JSON with a validator (a missing comma breaks the whole file)
npx not found / server fails to start	Install or update Node.js LTS; on Windows try npm install -g npm
Works in one folder, not another	Add that folder to the server’s args
Custom connector can’t connect to localhost	Expected; use an extension or the config file for local servers
Something else	Read the logs (below)

Logs live in ~/Library/Logs/Claude/ on macOS and %APPDATA%\Claude\logs\ on Windows. mcp.log covers connections, and mcp-server-NAME.log holds each server’s errors. On macOS:

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

Good first servers

• Files: the filesystem server above, limited to one or two folders.
• Browser: Playwright MCP lets Claude open pages and fill forms.
• Up-to-date docs: Context7 for current library documentation.
• GitHub: the GitHub MCP server for issues and pull requests.

Our best MCP servers list ranks more, and the MCP servers for Claude guide explains how MCP works in more depth.

Stay safe

• A local server runs with your account’s permissions. Give it the narrowest folders and keys you can.
• Install extensions and servers only from sources you trust, and remove ones you stop using.
• Read what a tool is about to do before you approve it.
• Never paste API keys into a chat; keep them in the extension settings or the env block.

Moving to Claude Code later

If you start coding with Claude, you can reuse this setup. On macOS and WSL, Claude Code imports your desktop servers with one command:

claude mcp add-from-claude-desktop

See getting started with Claude Code, or build your own server with our TypeScript MCP server tutorial.

MCP in your Claude kit

Connectors and servers are the part of a Claude kit that lets Claude act, not just answer. Two or three well-chosen ones beat a dozen you never use.