Using Claude

When MCP Connectors Won't Connect: Causes and Fixes by Symptom

Diagnose MCP connector failures by symptom: how remote connectors connect via the cloud, firewall/private-network blocks, OAuth and admin consent, chat toggles, the Free 1-connector limit, and SSE/HTTP — per official docs.

Sometimes you add an MCP connector but no tools appear, the connection times out, or you see "Need admin approval." Most of these trace back to a handful of predictable causes. This guide walks through narrowing the cause by symptom. Everything here follows the official Anthropic connectors docs. (As of June 2026.)

Remote connectors connect from Anthropic's cloudYour deviceClaude app/Desktop/CoworkAnthropic cloudYour MCP serverEven though Desktop/Cowork run locally, the connection originates from Anthropic's servers

First: remote connectors connect from the cloud

This is the most common misconception and the most common cause. A custom (remote) MCP connector reaches your server from Anthropic's cloud infrastructure, not your local device — the same across Claude web, Desktop, Cowork, and mobile. So even if Desktop or Cowork runs on your machine, the connection originates from Anthropic's servers. Your server must therefore be reachable over the public internet; if it sits behind a corporate firewall, VPN, or private network, the connection fails. In that case you must allowlist Anthropic's IP ranges in your firewall.

Diagnosis order when it won't connect1. Remote or local?remote=URL / local=npx·pip2. Reachable publicly?private net / VPN / firewall?3. Auth passed?OAuth sign-in & consent4. Enabled in chat?+ → toggle connector ON

Diagnosis order

  1. Remote or local? Distinguish a custom connector added by URL (remote) from a local server installed via npx/pip. Local stdio servers run in Claude Desktop and Claude Code; web and mobile support remote only.
  2. Reachable publicly? For a remote server, confirm the URL is accessible from outside. If it only opens on your PC but is blocked externally, Anthropic's cloud can't reach it.
  3. Auth passed? Most custom connectors use OAuth sign-in and consent. In an org, confirm admin consent is complete.
  4. Enabled in chat? Adding a connector to your account doesn't apply it to every conversation. Use the + button → Add connectors → toggle the connector ON for tools to appear.
Symptom → common causeTimeout after connectingServer not reachable publicly (firewall/private net)"Need admin approval"Org admin consent not completedAdded but no tools showConnector toggled OFF in chatCan't add on FreeFree is limited to 1 custom connector

Causes by symptom

  • Timeout after connecting → server not reachable over the public internet (firewall/VPN/private network). You may need to allowlist Anthropic IP ranges.
  • "Need admin approval" → org admin consent isn't complete. Only an Owner can add org connectors.
  • Added but no tools show → the connector is toggled OFF in that conversation. Turn it on via the + button.
  • Can't add on Free → free users are limited to one custom connector (the feature is in beta).
  • Remote server not detected in Claude Desktop → add remote servers via Settings > Connectors; remote servers configured directly in claude_desktop_config.json won't connect.

Note: Claude supports both SSE- and Streamable HTTP-based remote servers, and both authless and OAuth servers. Official docs note SSE support may be deprecated over time, so check this if your server uses only the older transport.

MCP connector security checkConnect only trusted servers (mind unverified ones)Review OAuth scopes before addingServers fetching external content = prompt-injection riskPrivate-network servers need Anthropic IP allowlistOnly an Owner can add org connectorsKnow the access/modify scope you grant

Security check before connecting

Custom connectors can link Claude to arbitrary services Anthropic hasn't verified. Connecting grants Claude the ability to read and modify data in that service within your permissions, so connect only servers you trust. Servers that fetch external content carry prompt-injection risk in particular. Review the scopes requested on the OAuth consent screen before adding.

Where to find connectors: where to find MCP servers; how to connect: connecting MCP; the concept: what is MCP.

Note: This article is based on Anthropic's official connectors documentation (accessed June 2026); plan limits, supported transports, and behavior may change. This site is not affiliated with Anthropic.

New here?: What Is MCP? (for non-developers)

Keep reading

What Is MCP? — A Simple Explanation for Non-Developers

Understand MCP (Model Context Protocol) without any coding knowledge. Covers the official 'USB-C for AI' analogy, before/after MCP, host and server, what you can do once connected, and safety — all at a beginner's level.

Where to find MCP servers — the official registry and connector directory

You don't have to build one. From the Claude app connector directory to the official MCP registry, GitHub reference servers, and marketplaces — paths to find and choose MCP servers.

Creating Your First CLAUDE.md — Start with One Line

A beginner's walkthrough of actually creating your first CLAUDE.md in Claude Code. Covers auto-generating with /init, doing it by hand, a short minimal example, the start-small-and-grow flow, and what to fill in first.

How to Read Claude Code Error Messages — A Beginner's Guide

So a red error in Claude Code doesn't faze you: how to read, classify, and handle error messages at a beginner's level. Covers automatic retries, the 5 kinds (server, usage, login, network, request), a calm 3-step approach, and /status and /doctor helpers.

Have a question or want to share how you use Claude?

Join the community to share tips with other users, or explore more guides.

Go to communityMore in Library