{"version":"2.1.139","anchor":"claude-ai-mcp-connector-diagnostics","canonical_anchor":"claude-ai-mcp-connector-diagnostics","heading":"Claude.ai MCP Connector Diagnostics","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.139\/e\/claude-ai-mcp-connector-diagnostics","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.139","markdown":"### Claude.ai MCP Connector Diagnostics\n\nClaude.ai MCP connector setup now reports clearer disabled states for third-party providers, API-key precedence, and missing `user:mcp_servers` scope.\n\n**Details**\n\n- Clarifies that claude.ai org connectors are disabled when the inference token lacks MCP scope.\n- Explicitly says locally configured MCP servers in `managed-mcp.json`, `.claude.json`, and `.mcp.json` are not affected.\n- Adds clearer provider-specific messages for third-party backends.\n\n**Evidence**\n\nMCP eligibility messages (search for `\"[claudeai-mcp] Disabled on third-party provider\"`, `\"inference token lacks user:mcp_servers scope\"`)"}