Set up your app
Adding custom connectors to Claude
By Sophie Filer · Updated 10 Nov 2026
A custom connector is a remote MCP server you add to your Claude account by its URL. Add it once on claude.ai and it follows you to Claude Desktop and the mobile apps, with no config file to edit.
- Add at
- Customize → Connectors
- Works in
- claude.ai, Claude Desktop, iOS and Android
- Local servers
- No (use the config file)
- Remote URLs
- Yes, one on Free
At a glance
- Step 1
1. Copy a URL
Pick a server that has a remote URL.
- Step 2
2. Add custom connector
Customize → Connectors → Add.
- Step 3
3. Paste and sign in
Keep the sign-in settings Claude detects.
- Step 4
4. Switch it on
Use + → Connectors in a chat, then ask.
Connectors in one minute
Claude has two kinds of connectors. Directory connectors are the ones Anthropic lists for you, such as Google Drive, Slack or Linear: you click Connect and sign in. Custom connectors are any other remote MCP server: you paste its address, and Claude treats it the same way. Both live in the same list, under Customize → Connectors.
The thing to know before you start: a custom connector is a URL, not a program. Claude cannot start npx or uvx from the browser. For a server that runs on your own computer, use the Claude Desktop config file or Claude Code instead. Remote or local explains the difference.
| Plan | Custom connectors |
|---|---|
| Free | One custom connector |
| Pro, Max and Ultra | As many as you like, added by you |
| Team and Enterprise | An Owner adds it to the organisation first; then each person connects their own account |
Add a custom connector (Free, Pro and Max)
- Step 1: Copy the server’s remote URL. On MCP Shelf it is on the server page, and the full list is further down this guide. It usually ends in
/mcp. - Step 2: Open claude.ai (or Claude Desktop) and go to Customize → Connectors.
- Step 3: Click Add (the + button) and choose to add a custom connector. Some versions show this as Custom → Web.
- Step 4: Give it a name. This is the name you will see in the connector list and in chats.
- Step 5: Paste the URL and click Continue. Claude checks the server and fills in the sign-in settings it detected.
- Step 6: Review the sign-in settings (explained below), change them only if the server’s README says to, and click Add.
- Step 7: If the server uses OAuth, click Connect and sign in to the service in the window that opens.
The sign-in settings, explained
| Setting | Options | Which to pick |
|---|---|---|
| Authentication | Sign in now, Sign in when needed, No sign in | Leave what Claude detected. "No sign in" is only for public servers such as Context7 or Microsoft Learn. |
| OAuth client | Use Claude’s published identity, Register automatically, Use your own OAuth client | Claude’s published identity, unless the vendor gave you a client ID to use. |
| Request headers | Any header name and value | For servers that want a fixed API key or bearer token instead of OAuth, such as Authorization: Bearer YOUR_KEY. |
Header values are stored encrypted. On a Team or Enterprise plan everyone who uses the connector shares that one key, so create a key with only the access your whole team should have.
Team and Enterprise: the Owner adds it first
- Step 1: An Owner or Primary Owner opens Organization settings → Connectors and clicks Add, then Custom → Web.
- Step 2: They enter the name and URL, review the detected sign-in settings, add any request headers, and click Add.
- Step 3: Each member then opens Customize → Connectors, finds the connector (it usually has a Custom label) and clicks Connect to sign in with their own account.
Because each person signs in for themselves, Claude only reaches what that person can reach in the service. Owners can also mark each tool as Always allow, Needs approval or Blocked, for example to let Claude read Jira issues but never create them.
Use it in a chat
- Step 1: In a chat, click the + button at the bottom left (or type
/) and open Connectors. - Step 2: Switch on the connectors this conversation needs. Leaving the others off keeps the tool list short and Claude more accurate.
- Step 3: Ask for something the server does, such as "find the open Sentry issues for the checkout service".
- Step 4: Claude asks before each tool call. Choose "Allow always" only for tools you trust to run without you watching.
A connector you add on the web or in Claude Desktop appears in the Claude iOS and Android apps the next time you sign in there. With ten or more connectors switched on, set Tool access to On demand in the same menu, so Claude loads tools only when it needs them.
When it will not connect
- Claude reaches your server from Anthropic’s cloud, not from your computer. A
localhostaddress, a server on your office network or one behind a VPN will fail, even if it opens fine in your own browser. Use a public HTTPS address, or have your network team allow Anthropic’s IP ranges. - Check the whole URL, including the path.
https://mcp.example.comandhttps://mcp.example.com/mcpare different addresses, and only one of them is the server. - Test the URL with MCP Inspector. If it fails there too, the server is the problem, not Claude.
- If sign-in fails or loops, remove the connector from Customize → Connectors and add it again.
- On Free, you already have your one custom connector. Remove it to add another.
- On Team or Enterprise, the Add button only shows for Owners. Ask one to add the server, or use the Request button on a directory listing.
Servers on MCP Shelf with a remote URL
Every server below has a hosted address you can paste as a custom connector. Open its page for the sign-in it needs and the tools it gives Claude.
| Server | Remote URL | Also runs locally |
|---|---|---|
| Context7 | https://mcp.context7.com/mcp | Yes |
| GitHub | https://api.githubcopilot.com/mcp/ | No |
| Exa | https://mcp.exa.ai/mcp | Yes |
| Supabase | https://mcp.supabase.com/mcp | No |
| Notion | https://mcp.notion.com/mcp | Yes |
| draw.io MCP | https://mcp.draw.io/mcp | Yes |
| GitMCP | https://gitmcp.io/docs | No |
| Apify | https://mcp.apify.com | Yes |
| AWS Knowledge MCP Server | https://knowledge-mcp.global.api.aws | No |
| TradingView MCP | https://mcp.tradingmcp.ai/mcp | Yes |
| Cloudflare MCP Servers | https://mcp.cloudflare.com/mcp | No |
| Perplexity MCP | https://api.perplexity.ai/mcp | Yes |
| Tavily MCP | https://mcp.tavily.com/mcp/ | Yes |
| Azure DevOps MCP | https://mcp.dev.azure.com/YOUR_ORGANIZATION | Yes |
| Terraform MCP Server | https://mcp.terraform.io/mcp | Yes |
| Ref MCP | https://api.ref.tools/mcp?apiKey=YOUR_REF_API_KEY | Yes |
| Neon MCP Server | https://mcp.neon.tech/mcp?readonly=true | No |
| Sentry MCP | https://mcp.sentry.dev/mcp | No |
| Microsoft Learn MCP | https://learn.microsoft.com/api/mcp | No |
| Postman MCP Server | https://mcp.postman.com/minimal | No |
| Stripe MCP | https://mcp.stripe.com | No |
Questions
Are Claude connectors the same as MCP servers?
Yes. A connector is Claude’s name for a remote MCP server added to your account. Directory connectors are ones Anthropic lists; custom connectors are any other server you add by URL.
Can I add a local MCP server as a connector?
No. Connectors are reached from Anthropic’s cloud, so they need a public URL. Add local servers to Claude Desktop’s config file or to Claude Code.
Do custom connectors work on the free plan?
Yes, but Free accounts can have one custom connector at a time. Pro, Max and Ultra can add as many as they need.
My server wants an API key, not a sign-in. Can Claude send it?
Yes. Add the key under Request headers when you add the connector, for example Authorization: Bearer YOUR_KEY. Use the narrowest key the service lets you create.
Do connectors I add on claude.ai work in Claude Code?
Claude Code keeps its own list. Add the same URL there with claude mcp add --transport http NAME URL; the Claude Code guide has the details.
Plant Your First Pea
Every server on the shelf has a tab with the exact config for your app.
For bots & AI agents
Machine-readable versions of this guide and MCP Shelf. Fetch these instead of parsing this page.
This guide (.md)llms.txtllms-full.txtai.txtFull catalog (.md)API specMCP serverMCP manifestDeveloper docs