What is an MCP connector?
An MCP connector is the name Claude and similar chat apps give a remote MCP server attached to your account. You add it from the Connectors directory or by pasting a server URL, sign in once, and Claude can then read from that service and act in it, in claude.ai, the desktop and mobile apps, Claude Code and Cowork.
Part of Glossary: the terms behind MCP, coding agents and shared pages, defined plainly.
Open Customize, then Connectors, in claude.ai or the desktop app. Pick a listing from the directory, or choose Add custom connector and paste the server's URL.
Claude detects how the server signs people in. Most use OAuth: the service's page opens, you approve, Claude keeps the token. Some take a key in a header.
Claude reaches the server from its own side, not from your machine, so the URL has to answer on the internet. A server on a private network needs a tunnel.
In a chat, turn the connector on from the + menu. Claude asks before a tool runs; per tool you can choose Always allow, Needs approval or Blocked.
Disconnect signs Claude out and keeps the entry; Remove drops it from your account. A name or URL can be edited; to change sign-in settings, remove and re-add.
Connector versus MCP server versus desktop extension
An MCP server is the program that answers tool calls. A connector is Anthropic's packaging of a remote one for a Claude account: the address, the sign-in you completed, the per-tool permissions you set, and a listing in the directory if its maker submitted it for review. The word belongs to the chat product, not to the protocol; the MCP spec never uses it. Other chat apps attach remote servers in much the same way and sometimes borrow the same word.
A desktop extension is the other kind. It runs on your computer inside the Claude desktop app, packaged as an MCP Bundle, and can reach your files. Connectors cannot, because Claude connects to them from Anthropic's infrastructure. If a server is only useful next to your filesystem, it is a desktop extension or a Claude Code server, not a connector.
Why it matters
Before connectors, giving a chat model access to a service meant a developer wiring up an API key on a server somewhere. With a connector the person who owns the account does it in a minute, with the service's own sign-in page and a token the service can revoke. For teams it also moves the decision to the right place: an Owner decides which servers the organization offers, and each member signs in as themselves, so access follows the person rather than a shared secret.
The trade-off is that the connection runs through Anthropic. Your server must be public, and the help page is direct that custom connectors reach services Anthropic has not checked. The permission prompt before each tool call is the control you have, so keep it on for anything that writes.
Common mistakes
- Pointing a custom connector at localhost or an office network. Claude cannot reach it. Put the server on a public address, use a tunnel for a private network, or use a desktop extension for local work.
- Clicking Always allow on a write tool from a server you barely know. A server's results can carry injected instructions. Keep approval on for tools that create, modify, send or delete, and set tools you never need to Blocked.
- Expecting a free plan to hold a full set. Free accounts get one custom connector.
- Trying to change a connector's sign-in settings in place. The name and URL can be edited; OAuth credentials and request headers cannot. Remove the connector and add it again, and members reconnect.
FAQ
- Are Claude connectors the same thing as MCP servers?
- A connector is an MCP server seen from the Claude side: the remote server plus your saved sign-in and tool permissions. Any remote MCP server can become a custom connector. The directory adds a layer of review, with each listing marked Verified or Community.
- Who can add an MCP connector on a Team or Enterprise plan?
- An Owner adds it for the organization from Organization settings, then Connectors. Members connect to it with their own account afterwards, so each person gets only what they are allowed to reach, unless the connector uses one shared key in a request header, which gives everyone the same access.
- Can a connector run on my own computer?
- Not as a remote connector; Claude would have to reach your laptop from Anthropic's servers. The desktop app has a separate path for local servers, packaged as desktop extensions (MCPB), and Claude Code can start local servers itself. Those do not appear in claude.ai or the mobile app.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.