Once you know what MCP (Model Context Protocol) is, the next question is how to actually connect it. There are four main ways to connect MCP to Claude, from the easy Directory connectors to Claude Code for developers. (New to the concept? Start with What is MCP?)
🟢 Model references match the current lineup · model notice · Fable subscription
Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (
- Four ways to connect MCP — directory connector (easiest) · custom (remote) · local (Desktop) · Claude Code.
- Non-developers should start with the directory connector.
- Remote custom uses URL + auth, local uses a config file, Claude Code uses the terminal.
- Always verify a server's trustworthiness and security before connecting.
1. Directory connectors (easiest)
Popular, ready-made connectors like Google Drive, Slack, and GitHub take just a few clicks.
- Click the "+" button at the lower-left of the chat box, or type "/" to open the menu.
- Choose Connectors to open the directory. Browse by category or scroll the full list.
- Pick an app and complete the OAuth sign-in. Review the access it requests during connection.
After connecting, you don't have to name the app every time — Claude brings the tool into the conversation on its own when it fits your request. The directory is available on claude.ai, Claude Desktop, and the iOS/Android apps.
📍 Exact button location (official, 2026): Per Anthropic's connectors help article, you can also add directory connectors from Customize > Connectors (or open claude.ai/settings/connectors): click the "+" button next to Connectors, pick a service, then click "Connect" (or "Install"). Directory connectors work on every plan including Free; custom connectors allow one on Free and more on paid plans.
2. Custom connectors — remote MCP servers
To connect your own server or an internal service, use a custom connector.
- Go to Customize > Connectors (or open claude.ai/settings/connectors).
- Choose "Add custom connector."
- Enter the server URL (e.g.
https://your-server.example.com/mcp) and any required auth.
⚠️ Important: Custom connectors connect from Anthropic's cloud to your server (not from your PC). So the server must be reachable over the public internet — servers behind a firewall, VPN, or private network won't connect. Use Streamable HTTP (SSE may be deprecated). Custom connectors link to services not verified by Anthropic, so only connect servers from trusted organizations and review permissions carefully.
3. Local MCP servers — Claude Desktop
To reach local tools and files on your own computer, use Claude Desktop's config file (a separate mechanism from remote connectors; runs locally over stdio).
Config file location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Example (filesystem server):
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
}
}
}Save and restart Claude Desktop. Use "+" > Connectors to see connected MCP servers and their tools; you can also install .mcpb desktop extensions. Note: local MCP isn't available on claude.ai web or Cowork.
4. Claude Code (developers / terminal)
From the terminal, add an MCP server in one line.
# Basic syntax
claude mcp add --transport http <name> <url>
# Example: connect Notion
claude mcp add --transport http notion https://mcp.notion.com/mcpServers that need auth support OAuth 2.0; if the server returns 401/403, complete the flow from /mcp. HTTP transport is the most widely supported for remote connections.
For a step-by-step walkthrough of adding a custom connector in Claude Code (remote HTTP, local stdio, scopes, auth, and common snags), see Adding a Custom Connector to Claude Code.
You can also use the MCP connector in the Claude API to connect public HTTP MCP servers directly from the Messages API (for developers — see the platform.claude.com docs).
Handy terminal tips
- Local servers go after
--: remote servers use--transport httpas above; a local server takes its launch command after--, e.g.claude mcp add <name> -- npx -y @modelcontextprotocol/server-filesystem ~/projects. - On Windows, wrap npx in
cmd /c: e.g.claude mcp add my-tool -- cmd /c npx -y <package> - When a server drops: if
claude mcp listshows it asdisconnected, restart Claude Code. - Too many tools eat context: when tool definitions exceed ~10% of the context window, Tool Search automatically loads only the tools you need.
- Connect production databases with a read-only account so an accidental write or delete cannot happen.
Popular connectors
Commonly used directory connectors include Google Drive, Slack, GitHub, and Notion. Each connector page shows its read/write capabilities and availability. (These are representative examples, not a ranking.)
Security check
- Connect only trusted servers. A custom/unverified server lets Claude read data and take actions in that service.
- Review the access requested at connection time. Only data you can already view in the source is synced.
- All data transfers are encrypted.
Frequently asked questions
How do I add a connector to Claude?
The easiest way is to enable a service from the Claude app's directory connectors — a few clicks, no dev knowledge needed. For more flexibility, use a custom connector or Claude Code.
How do I add a custom connector?
Enter the remote MCP server's URL and complete the required auth (usually OAuth or an API key). Note that custom connectors aren't vetted by Anthropic, so confirm the server is trustworthy first.
Which servers can I connect?
Representative servers by use case are in recommended MCP servers, and where to find them is in where to find MCP servers.
What if the connector won't connect?
Expired auth, a wrong URL, or a server outage are common causes. For symptom-by-symptom checks, see MCP server troubleshooting.
Are connectors safe?
Directory connectors are relatively safe, but connect a custom connector only when you trust its source. Keep permissions minimal; for safety rules, see connector security.
Which Method Should You Use? (30-Second Decision)
Before diving into setup steps, pick your method. Answer two questions:
| Your situation | Best method | Skill level |
|---|---|---|
| You just want a popular tool (Notion, GitHub, Google Drive) connected right now | Directory Connector | ★☆☆ Beginner |
| You have a URL for a third-party or self-hosted MCP server | Custom Remote MCP | ★★☆ Intermediate |
| You want to run an MCP server locally on your machine via Claude Desktop | Claude Desktop config file | ★★☆ Intermediate |
| You are writing or testing code and use the terminal daily | Claude Code (CLI) | ★★★ Developer |
Most Common Errors & Fixes
These are the points where beginners most often get stuck. Match your error message or symptom below.
🔴 Symptom: The connector toggle is grayed out or missing on claude.ai
Cause: Directory connectors require a Claude Pro or Team plan. The Free plan does not show the Integrations section.
Fix: On claude.ai, open the left sidebar and check your plan under your account name. Upgrade if needed, then navigate to Settings → Integrations to see the connector list.
🔴 Symptom: Claude Desktop shows no MCP tools after editing the config file
Cause (1): JSON syntax error — a missing comma or brace stops the file from loading silently.
Fix: Paste your config into jsonlint.com and fix any errors shown, then save the file and fully quit and reopen Claude Desktop (Cmd+Q on Mac / right-click tray icon → Quit on Windows).
Cause (2): The app was not fully restarted — closing the window is not enough.
Confirmation signal: After restart, open a new conversation. Type / or look for a tools icon in the input bar. If your MCP server name appears in the list, the connection succeeded.
🔴 Symptom: claude mcp add returns "command not found"
Cause: Claude Code is not installed or not on your system PATH.
Fix: Run npm install -g @anthropic-ai/claude-code first, then open a new terminal window and retry. Verify installation with claude --version — you should see a version number printed. If PATH is still not found, check the install path shown by npm root -g and add it to your shell profile.
⚠️ Security reminder: When adding any custom remote MCP server, only use URLs from sources you trust. A malicious server can read the data you send it. Treat an MCP server URL like a browser extension — vet it before installing.
Looking for more connectors? Browse the connector directory to search and filter common connectors by use case.
Related articles
- What Is MCP (Model Context Protocol)? Architecture and Security
- Recommended MCP Servers for Claude, by Use Case (2026)
- Claude Code MCP Setup: claude mcp add, Scopes, and Transports
- Connect Claude to Figma: Figma MCP (Dev Mode) Setup for Claude Code (2026)
- Build Your Own MCP Server: From First Python Server to Claude (2026)