Claude.ai MCP Connector Diagnostics / Claude Code v2.1.139

Claude.ai MCP connector setup now reports clearer disabled states for third-party providers, API-key precedence, and missing user:mcp_servers scope.

Details

Clarifies that claude.ai org connectors are disabled when the inference token lacks MCP scope.
Explicitly says locally configured MCP servers in managed-mcp.json, .claude.json, and .mcp.json are not affected.
Adds clearer provider-specific messages for third-party backends.

Evidence

MCP eligibility messages (search for "[claudeai-mcp] Disabled on third-party provider", "inference token lacks user:mcp_servers scope")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agree/mcp Reconnect now picks up .mcp.json edits without a restart, and shows the HTTP status and URL when reconnecting fails

See this entry in the whole of v2.1.139 →

The build it came inv2.1.139

11 May 2026 · 13 entries, this one is #8.

Either side of it

v2.1.138Older
v2.1.140Newer

Open the release →

Names in this entry

settinguser
Recalled memories no longer get silently dropped when the model echoes back the category label with the name.

Anthropic's note

Upstream's own release notes for v2.1.139 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

/mcp Reconnect now picks up .mcp.json edits without a restart, and shows the HTTP status and URL when reconnecting fails

Is this right?