How to Add an MCP Server to Claude (Step by Step)

MCP stands for Model Context Protocol. It is an open standard that lets an AI app like Claude use outside tools: your files, a database, a calendar, a tool your team uses. Each one runs as an MCP server. Claude connects to it and can then read data or take actions, based on what you allow.

There are two ways to connect a server:

Local server: the server runs on your computer. You add it to a config file in Claude Desktop. Best for files and tools on your own machine.
Remote server (custom connector): the server runs on the internet. You add its web address in Claude’s settings. Best for hosted services.

This guide covers both. Menu names can change between app updates, so if a label looks different, look for the same idea nearby.

Before you start

Claude Desktop installed (Windows or macOS), updated to the latest version.
Node.js installed, LTS version. Check it by opening a terminal and typing node --version. If you see a version number, you’re set. If not, download it from nodejs.org.
For a remote server: a Claude plan that supports custom connectors. Free plans can add one.

Part 1: Add a local server (file access example)

We’ll use the official Filesystem server. It lets Claude read, create, move and search files inside only the folders you choose.

Step 1: Pick one folder for Claude to use. Create a test folder, for example C:\Users\YourName\Documents\ClaudeTest. Put a few text files in it. Keep it small for now. You can add more folders later.

Step 2: Open the config file. In Claude Desktop, open Settings, then the Developer section, then Edit Config. This opens claude_desktop_config.json.

You can also open it directly:

Windows: %APPDATA%\Claude\claude_desktop_config.json (paste this into the File Explorer address bar)
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Step 3: Paste this configuration. If the file is empty, paste the whole block. If it already has content, add only the "filesystem" part inside the existing "mcpServers" section, with a comma between entries.

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

Replace the folder path with your own. On Windows, use double backslashes (\\) as shown. Keep the quotes and commas exactly right: one missing comma will stop the server from loading.

Step 4: Save and fully restart Claude Desktop. Closing the window is not enough on Windows. Quit the app from the system tray or the menu, then open it again. Claude only reads the config at startup.

Step 5: Check that it loaded. Open a new chat. Look for the tools or connectors icon near the message box. The filesystem server should appear. If it doesn’t, open the logs from the Developer settings and check the error.

Step 6: Try a safe test. Type:

List the files in my ClaudeTest folder and tell me what each one is about.

Claude will ask for permission before using the tool. Read the request, then approve it. You stay in control of every action.

Part 2: Add a remote server (custom connector)

Use this when a company or developer gives you a web address for an MCP server.

Step 1: Get the server’s URL. It must start with https://. Copy it exactly. Only use servers from people or companies you trust.

Step 2: Open the connectors screen. In Claude, go to Settings, then Connectors. Choose Add custom connector.

Step 3: Paste the URL and add a name. Give it a name you’ll recognise, for example “Team tasks”. Save.

Step 4: Sign in if asked. Some servers open a login page. Sign in through that page only. Read the permissions it asks for, and deny anything that looks unnecessary.

Step 5: Turn it on in a chat. Start a new chat, open the connectors menu, and make sure your new connector is switched on for that chat.

A note on private servers. Remote connectors are reached from Anthropic’s cloud, not from your laptop. If your server sits on a private company network or behind a VPN, it won’t connect until its firewall allows Anthropic’s IP ranges. Anthropic publishes those ranges in its API documentation.

Safety checks before you approve anything

Connect only trusted servers. A malicious server can hide instructions in its tool replies. Read each tool request. Claude shows what it wants to do. If it asks to delete or send something you didn’t request, say no. Limit access. Give the filesystem server one folder, not your whole drive. Give remote services the smallest permissions they offer. Remove what you don’t use. Disconnect old servers from the config file or the connectors list.

Troubleshooting

If the server doesn’t appear, check the JSON for missing commas or quotes, then fully restart the app. If you see “npx not found”, Node.js isn’t installed, or the terminal needs a restart after you install it. If a remote connector won’t connect, check that the URL starts with https://, and check whether the server sits on a private network. If Claude says it can’t access a folder, the folder path in the config must match a real folder exactly.

What to try next

Once one server works, the same steps work for others. Start with one, check that it does what you expect, and only then add the next.

Sources

Model Context Protocol docs, “Connect to local MCP servers”: https://modelcontextprotocol.io/docs/develop/connect-local-servers
Anthropic Help Center, “Get started with custom connectors using remote MCP”: https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp

Checked on 8 October 2026. Anthropic’s apps change often, so if a menu name differs, the help center is the final word.

Related: Claude Haiku 5.5: Price, Benchmarks and the 100K Catch explains the model that powers the chats above.