The right route to connect Claude to an MCP server depends on whether the server is hosted for you, runs on your computer, or needs to be configured from a terminal. Plan and organization permissions decide who can add it.

Which Claude connectors should I use?

Choose the connectors directory for a ready-made service, a custom remote connector for a hosted MCP server, a desktop extension for a local MCP process, or Claude Code when you want the server configured in a coding terminal.

RouteWho can add itPlan or permissionWhere it runs
Directory connectorIndividual; Team/Enterprise owner may need to enable it firstAvailable by connector; check its listing and organization policyClaude web, Desktop and mobile where supported
Custom remote connectorIndividual account; Team owner/primary owner; Enterprise owner/primary owner or eligible custom roleFree through Enterprise; Free has one custom connectorAnthropic's cloud calls a public HTTPS MCP server
Claude Desktop local MCP or desktop extensionDesktop user; organization may restrict extensionsClaude Desktop; Team/Enterprise admins can manage extension accessYour computer, with local process permissions
Claude Code MCPAnyone who can configure Claude Code and authenticateClaude Code CLI; organization policy can restrict serversLocal process or remote endpoint, based on transport

Anthropic states that remote connectors are reached from its cloud even in Claude Desktop, while local MCP servers configured in Claude Desktop are a separate mechanism. That difference decides whether localhost can work: it can be relevant to a local Desktop server, but a web custom connector must be publicly reachable. See Anthropic's remote connector guide and local Claude Desktop MCP guide.

What are Claude connector plan limits?

As checked November 2026, Anthropic lists remote custom connectors on Free, Pro, Max, Ultra, Team and Enterprise. Free is limited to one custom connector. Team and Enterprise add an organization-owner step before members can connect individually.

Claude planCan use a custom remote connector?Add limit or gate
FreeYesOne custom connector per Anthropic's help page
ProYesCustom-connector count limit is not stated in the guide
MaxYesCustom-connector count limit is not stated in the guide
UltraYesAvailable; the guide does not state a connector count limit
TeamYesOwner or Primary Owner adds it for the organization; each member connects afterward
EnterpriseYesOwner, Primary Owner, or a custom role with Manage access to Libraries can add it; each member connects afterward

These are connector-specific limits, not Claude message-use allowances. Anthropic does not publish a count limit for the paid plans in the custom connector article.

During the UI transition checked November 2026, look under Customize → Connectors in the older layout, or open Plugins and filter to Connectors in the new layout; Plugins is rolling out to Free, Pro, Max, Ultra and Team, and is scheduled to reach Enterprise on November 30. The migration notice lists general availability for the first group as November 9.

How do I add a remote MCP server as a Claude custom connector?

Use a public HTTPS URL that Anthropic's servers can reach, then complete the detected authentication flow. We make Unsame, and here we add its engine, a remote MCP server for Claude, as the worked example; the same steps apply to another remote MCP server.

Have the server URL and a Claude account. On Team or Enterprise, ask an owner to add it first.

Claude connects from Anthropic's cloud, so a server on localhost cannot be added, and a server on a private network, behind a VPN or behind a firewall fails unless you allowlist Anthropic's IP ranges, even if it opens on your own computer. See Anthropic's custom connector network requirements.

  1. Open Customize → Connectors, click + Add, then Add custom connector. Anthropic is renaming Customize to Plugins; if your sidebar shows Plugins, that is the same place.
  2. Enter the name Unsame and this URL: https://api.unsame.io/mcp/engine. Select Continue.
  3. Review the authentication settings Claude detects. Choose the sign-in option that matches the server; Unsame uses OAuth, so finish the browser sign-in when prompted. Do not paste an API key.
  4. Finish adding the connector. On Team or Enterprise, an owner uses Organization settings → Connectors to add the URL; members then find it in their connector list and select Connect.
  5. In a chat, click + → Connectors and turn on Unsame for that conversation.
  6. Ask Claude to list your goals. A goal list confirms the server connected and its tools are available.
  7. To remove it later, open Customize → Connectors and click Remove, or the three dots next to the connector. A Team or Enterprise owner removes an organization connector under Organization settings → Connectors. To change a connector's URL or sign-in settings, remove it and add it again; Anthropic does not allow editing in place.

Free includes one custom connector, so add only the engine URL on that plan. Unsame also has an optional author server at https://api.unsame.io/mcp/author; on Free, edit the playbook in Unsame instead of using a second connector.

The Unsame MCP setup docs cover the other supported apps. Claude Desktop uses the same remote custom connector route; for a server that must run locally, choose a Desktop extension instead.

How do I enable a Claude connector in a chat?

In the chat composer, click +, open Connectors, and enable the connector's toggle; confirm it remains enabled in that chat before asking Claude to call a tool.

When the setup is complete, you can use Unsame's goal prompt once in that chat to tell Claude which goal and scope to use. The optional sign-in page is where you can create or open an Unsame account.

Why is my Claude connector not working?

The errors usually come from chat-level tools being off, a remote URL Claude cannot reach, incomplete sign-in, or organization permissions.

SymptomLikely causeFix
Connector is connected but tools do not appear in this chatIts per-chat toggle is offClick + → Connectors and turn it on for this conversation.
URL uses localhost, a private IP, VPN, or internal hostRemote custom connectors connect from Anthropic's cloud, not your laptopDeploy it to a public HTTPS host or use Claude Desktop's local MCP/extension route.
Authentication failsSign-in did not finish, or the connector was added with the wrong sign-in settingsDisconnect and reconnect from Customize → Connectors. If the settings were wrong, remove the connector and add it again with the right ones; they cannot be edited after adding.
Team member cannot see Add custom connectorOrganization-level connector changes are owner-gatedAsk an Owner or Primary Owner to add it under Organization settings → Connectors, then connect from your account. On Enterprise, a custom role with the required Library permission can also add it.

Anthropic's connection troubleshooting page recommends disconnecting and reconnecting after authentication failures, and confirms the public-network requirement for custom remote connectors. For a local Desktop extension that installed but exposes no tools, restart Claude Desktop and check its required settings and credentials in the Desktop extension guide.

Claude Code is a separate CLI route: use it when you want MCP configuration attached to your coding terminal, following Anthropic's Claude Code MCP reference.

— Don