How to Use MCP Servers in Claude (Desktop and Web)

Short answer: Claude MCP servers come in two kinds. Remote servers connect from Customize > Connectors on the Claude website and in Claude Desktop, and you add one with a name and a URL. Local servers run on your own computer and need Claude Desktop, either through a config file or a desktop extension. Start with a remote server, because it works everywhere you use Claude.

An MCP server is a small program or hosted service that lets Claude read and act in another app, such as GitHub or your files. If you are new to the idea, read our guide on what MCP servers are first, then come back here for the exact steps. This post covers adding servers to Claude itself. If you work in the terminal, our Claude Code page covers that tool, which has its own setup.

MCP in Claude at a glance

Which kind of server should you pick?

Anthropic calls most connectors remote and treats them as the default choice, because they work on every Claude surface once connected. Pick a local server only when the tool has to touch something on your machine, such as a folder of files or a desktop app. Local servers are only available in Claude Desktop and Claude Code, not on the web or on mobile.

Our directory lists which servers are remote and which are local. Look for the hosting line on each server page, such as the one on GitHub MCP Server.

What you need first

• A Claude account. Custom remote connectors are open to the Free, Pro, Max, Team and Enterprise plans. Free accounts can add one custom connector.
• On Team and Enterprise plans, an admin may have to add or enable the connector for the organization before you can connect to it. On Team, only Owners and Primary Owners can add one. Each person then signs in on their own.
• For a local server, Claude Desktop and Node.js. Check Node.js with node --version in a terminal. The Node.js LTS release is the safe choice.

How to add a remote MCP server in Claude

There are two ways to add a remote server: pick one from the connector directory, or add your own by URL.

Option 1: Connect a server from the directory

1. In Claude, open Customize > Connectors and click the “+” button next to Connectors. From inside a chat you can also click “+”, hover over Connectors and choose Manage connectors.
2. Click the connector you want and read its description and capabilities.
3. Click Connect or Install, then follow the sign-in prompts.

Anthropic’s list of directory connectors includes Linear, Slack, Google Drive, Gmail, Google Calendar, GitHub and Microsoft 365. Our pages for Linear MCP, GitHub MCP Server, Slack MCP, Google Drive MCP and Gmail MCP show how each one signs in and what it can do.

On Team and Enterprise plans, an Owner must enable a directory connector for the organization first. Then each person connects with their own account.

Option 2: Add a custom connector by URL

Use this when the server is not in the directory but has a public MCP URL.

1. On a Pro or Max plan, go to Customize > Connectors, click “+ Add” and choose “Add custom connector”. On Team and Enterprise, an admin goes to Organization settings > Connectors, clicks “Add”, hovers over “Custom” and selects “Web”. Members then go to Customize > Connectors and click Connect.
2. Enter a name. This is what you see in your connectors list.
3. Enter the remote MCP server URL. For example, the Linear MCP page lists https://mcp.linear.app/mcp, and the GitHub MCP Server page lists https://api.githubcopilot.com/mcp/.
4. Choose how to sign in: “Sign in now”, “Sign in when needed” or “No sign in”. For OAuth servers you can use Claude’s published identity, register automatically or bring your own OAuth client. If the server uses a fixed API key or bearer token instead, add it as a request header.
5. Save, then complete the sign-in when Claude asks.

Two limits to know. The server must be reachable over the public internet, so a server on a private network needs an allowlist. And you cannot edit a custom connector after you save it. To change one, remove it and add it again.

Turn connectors on for a conversation

Open a chat, click “+” at the lower left and choose Connectors. Each connector has a toggle. You can also use the “Search and tools” menu to switch off single tools that you do not want Claude to call. Read-only tools are a good place to start.

How to add a local MCP server in Claude Desktop

Local servers are set up in Claude Desktop. The steps below use the Filesystem MCP Server, which is the reference server for local file access.

1. Open the Claude menu in your system menu bar and choose Settings. This is the Claude Desktop settings window, not your account settings.
2. Go to the Developer tab and click Edit Config. This opens, or creates, the file claude_desktop_config.json. On macOS it is at ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it is at %APPDATA%\Claude\claude_desktop_config.json.
3. Put the server in the file. This macOS example gives the server access to two folders:

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

1. Replace username with your own username. On Windows, use paths such as C:\\Users\\username\\Desktop with double backslashes.
2. Save the file, quit Claude Desktop completely and open it again. It reads the config only at start.
3. To check the server, click the add-files control (the one whose label begins “Add files”) at the bottom left of the message box, hover over Connectors and click Manage connectors. Pick filesystem from the list to see its tools.

The server runs with your own account permissions, so list only folders you are happy for Claude to read and change. Claude asks for your approval before each file action.

The same pattern works for other local servers. Our Playwright MCP page lists the command npx @playwright/mcp@latest for driving a real browser, and it names Claude Desktop among the apps it works with.

Prefer a one-click install? Use a desktop extension

Claude Desktop also installs local servers as extensions packaged as .mcpb files, with no config file to edit. Go to Settings > Extensions, browse the directory and click Install, then fill in any settings such as an API key. For your own file, open Advanced settings, find the Extension Developer section and click “Install Extension…”. Claude Desktop includes a built-in Node.js environment for extensions, so you do not need to install Node.js separately.

Which servers to add first

Start with a few that you will use every day, and leave the rest.

• GitHub MCP Server: read repos, manage issues and pull requests and check Actions runs. Free, with a GitHub account.
• Linear MCP: find, create and update issues and projects. Free, with a Linear account.
• Filesystem MCP: let Claude work with files in folders you choose. Free and local.
• Playwright MCP: drive a browser to test or read web pages. Free and local.

For more by job, browse the browser and web servers or the full MCP servers directory.

Common problems and fixes

• The server does not show up in Claude Desktop. Quit and reopen the app completely. Check the JSON for typos, and make sure every folder path is absolute rather than relative.
• A local server will not start. Run the same npx command in a terminal to see the error. Check that Node.js is installed.
• You need the logs. Claude Desktop writes MCP logs to ~/Library/Logs/Claude on macOS and %APPDATA%\Claude\logs on Windows. The file mcp.log covers connections, and mcp-server-SERVERNAME.log holds each server’s own output.
• A remote connector will not connect. Confirm the URL is public and the sign-in method matches what the server expects. Remove the connector and add it again if you need to change a setting.
• A Windows path error mentioning ${APPDATA}. The MCP docs say to add the expanded value of %APPDATA% to the env key for that server, and to install npm globally if npx keeps failing.
• Tools are missing in a chat. Check the “+” menu and make sure the connector is switched on for that conversation.

What MCP servers in Claude cannot do

Connectors reach only what the server exposes and what your account allows. A custom connector points at a service Anthropic has not verified, and a malicious server could try to push hidden instructions to Claude through the text it returns. Read what a tool is about to send or change before you approve it. In Research, Claude can call connector tools without asking each time, so switch off write-capable tools before you run it. Advanced research cannot call tools from local servers at all. And a shared credential on a team connector gives everyone the same access.

If a task only needs a quick look at one file, you may not need a server. Paste the text in instead. Add a server when you will repeat the work.

FAQ

Do MCP servers work in Claude on the web?

Yes, remote ones do. You add them from Customize > Connectors in your browser. Local servers only work in Claude Desktop and Claude Code, not on the web or on mobile.

Are MCP servers free in Claude?

The connector feature is open on every plan, and free accounts can add one custom connector. The cost of a server depends on the service behind it. GitHub MCP and Linear MCP are free to use but need an account with the vendor.

Where is the Claude Desktop MCP config file?

On macOS it is ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it is %APPDATA%\Claude\claude_desktop_config.json. The quickest way to open it is Settings > Developer > Edit Config.

What is the difference between a connector and an MCP server?

In Claude, a connector is how an MCP server shows up in your settings. Remote servers appear as connectors you add with a URL or from the directory. Local servers run on your machine and also appear in the Connectors list once they start.

Is it safe to add an MCP server to Claude?

It is as safe as the server you trust. Stick to servers from the vendor of the tool, check which tools you are enabling and keep write access off until you need it. Our directory marks which servers are official, and each page shows how it signs in.

Can I use the same servers in Claude Code?

Often yes, because most servers work in more than one app. Claude Code has its own setup, so check the server’s page for the command or URL. Our Claude Code page and the Codex vs Claude Code guide cover the terminal side.

The steps here come from Anthropic’s help article on custom connectors and the MCP project’s guide to connecting local servers, checked in October 2026. Menus change often, so follow Anthropic’s page if a label differs. To see what is out there, browse the Klyvoo MCP servers directory.