What
An MCP server can now be marked disabled for a project and shows "Disabled in /mcp" with its own status badge instead of a generic failure. Connection errors gained three codes: POLICY_BLOCKED for a server blocked by enterprise managed policy, DISABLED for one turned off locally, and IDENTITY_CHANGED for a reconnect that raced an account switch.
Details
- The blocked-by-policy row reports "Blocked by enterprise managed policy".
- A reconnect cancelled by an account change gets a dedicated message and logs
mcp_reconnect_identity_changed.
Evidence
Disabled for this project (re-enable via /mcp)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/mcp
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Channels reference touched a line naming /mcp after this was published.
* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de…channels-reference see the edit
Confirmed since
Anthropic's documentation has since written up /mcp, on Third party connectors with remote MCP.
**MCP server URL**: the HTTPS address where the server accepts MCP requests, for example `https://mcp.example.com/mcp`. After you continue, Claude checks the URL and pre-fills the authentication settings it detects, marked "Detected."connectors/custom/remote-mcp see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /mcp, on Third party connectors with remote MCP.