How to add a custom connector to Claude
In claude.ai open Customize, then Connectors, choose "+ Add" and "Add custom connector", paste the server's address and sign in when asked. On Team and Enterprise only an Owner (or, on Enterprise, a custom role with access to Libraries) can add one for the organization, and members then press Connect. Free plans can add one. A connector added on the web also appears in Claude Desktop and, once you sign in, on the phone apps.
Checked against Anthropic's help pages on 18 November 2026.
Who can add one, by plan
| Question | Free | Pro, Max, Ultra | Team | Enterprise |
|---|---|---|---|---|
| Can you add a custom connector? | Yes | Yes | Owners and Primary Owners | Owners, Primary Owners and people with a custom role that includes "Manage access to Libraries" |
| How many? | One | No limit stated | No limit stated | No limit stated |
| Who signs in to the service? | You | You | Each member, individually, after the Owner adds it (or once for the organization with Enterprise-managed sign-in, in beta) | Each member, individually (or once for the organization with Enterprise-managed sign-in, in beta) |
| Org-wide limits on what it can do | Not applicable | Not applicable | Owners can set each tool to Always allow, Needs approval or Blocked | Same |
Anthropic's wording: custom connectors are "available on Claude, Cowork, and Claude Desktop for users on Free, Pro, Max, Ultra, Team, and Enterprise plans", and "Free users are limited to one custom connector." Read 18 November 2026: custom connectors with remote MCP and using connectors.
Adding one on the web (Free, Pro, Max, Ultra)
- Open Customize, then Connectors. Older guides say Settings, then Connectors. That menu has moved.
- Click + Add, then Add custom connector. On some accounts the same step reads Add, then hover over Custom and choose Web.
- Type a name and paste the connector's address (the remote MCP server URL), then click Continue.
- Check the sign-in settings Claude detected. Authentication can be "Sign in now", "Sign in when needed" or "No sign in". For the OAuth client, "Use Claude's published identity (Recommended)" is right for most servers. If the service uses a fixed key instead, there is a Request headers box.
- Click Add, then connect and sign in to the service when its window opens.
To use it in a conversation, click the "+" at the lower left of the chat, then Connectors, and switch it on. Typing "/" opens the same menu. With ten or more connectors active, Anthropic suggests switching Tool access to On demand.
Claude Desktop and the phone apps
Remote connectors belong to your Claude account, so a connector you add on the web is there in Claude Desktop too, and the connection to the server is made from Anthropic's servers, not from your computer. On iOS and Android it is available the next time you sign in. Adding connectors on a phone is in beta, and Anthropic says Claude Desktop and the web remain the main way to add custom ones. Servers you list in the Desktop file claude_desktop_config.json are a separate, local mechanism and don't show up in claude.ai.
Team and Enterprise: the Owner adds it
An Owner adds the connector for everyone: Organization settings, then Connectors, then Add, hover over Custom, choose Web, then name, address and the same sign-in choices as above. Members then open Customize, then Connectors, find it (it usually has a "Custom" label) and click Connect. Each person authenticates as themselves, so Claude can reach only what that person can reach, unless the connector uses one shared key, in which case everyone gets that key's access.
The member "Request" button is not the route for a custom connector. Anthropic documents it only for connectors in its directory (on by default on Team, off on Enterprise). For a custom address, a member asks the Owner directly. Here is a message you can send:
Hi [name],
Could you add a custom connector to our Claude organization? In Organization settings > Connectors choose Add, hover over Custom, pick Web, and enter:
Name: [name of the service]
Address: [the connector address]
It is for [what we will use it for]. After that each of us signs in to it ourselves from Customize > Connectors. Thanks. Owners can also set what a connected service may do across the whole organization: Customize, then Connectors, select the connector, and under Tool permissions choose Always allow, Needs approval or Blocked for each category or tool. Individual members can't override it. For Haechy's connector in particular, the page for IT admins covers what it can reach and how to add or remove it.
What the sign-in asks, and how to undo it
A custom connector usually opens an OAuth sign-in window, drawn by the service you are connecting, so its wording differs from one connector to the next. Claude never sees your password. Read the permissions it asks for, and say no to any that look unnecessary. Anthropic also advises connecting only to servers you trust: it says it hasn't verified custom connectors.
To see what is connected, open Customize, then Connectors. For each service you can disconnect it, change settings or review its permissions. Removing a connector there, or disconnecting it in the service's own security settings, ends the access. To change a connector's details, remove it and add it again.
When it doesn't work
- "Unable to reach this address", or "Couldn't reach" when you turn it on. The server must be reachable from the public internet. A server on a company network, behind a VPN or behind a firewall won't connect, even if you can open it yourself. Allow Anthropic's IP addresses in the firewall.
- "Couldn't determine how this server signs in. You can continue and configure it manually." On 13 November 2026 several people reported this on GitHub, including for servers that worked the day before (issue 1270). Select Continue anyway and choose the sign-in settings yourself, or try again later.
- "Authorization with the MCP server failed", with a reference ID starting
ofid_. Disconnect the connector and connect it again from Customize, then Connectors. If it keeps failing, send the reference ID to whoever runs the server. - "This corporate identity belongs to an Enterprise that manages access through their own Claude account." Sign in to your organization's Claude account and connect the service there.
- No "Add custom connector" on Team or Enterprise. Only the roles in the table above can add one. Ask your Owner, with the message above.
- A second connector won't save on Free. Free plans are limited to one custom connector.
Claude Code and Codex are different
Claude Code reads servers from its own commands and files rather than this screen: add an MCP server to Claude Code. Codex has its own configuration file and commands: add Haechy to Codex.
A worked example: Haechy
Haechy runs apps your assistant builds. Its connector address is:
https://mcp.haechy.com/mcp Add it as a custom connector named Haechy, keep "Sign in now" and "Use Claude's published identity (Recommended)", and a Haechy sign-in window opens where you create your account or log in. Then try: "Put my team's stock-count app online with Haechy." Haechy is added as a custom connector and isn't in Anthropic's directory. The full steps, including what an Owner does on Team and Enterprise, are on Add Haechy to claude.ai.
Sources
- Get started with custom connectors using remote MCP, Anthropic, read 18 November 2026
- Use connectors to extend Claude's capabilities, Anthropic, read 18 November 2026
- User reports on GitHub, issue 1270, 13 November 2026
Haechy is an independent product of DT Global Ventures Ltd. It is not made, sponsored or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.