Claude.ai MCP Server Integration Improvements

What

Enhanced Claude.ai MCP server integration with better eligibility checking and telemetry.

Details

New eligibility states tracked: disabled_gate, disabled_env_var, no_oauth_token, missing_scope, eligible
Requires user:mcp_servers OAuth scope
Can be disabled via ENABLE_CLAUDEAI_MCP_SERVERS environment variable
Improved logging for debugging MCP server connectivity

Evidence

Q_0 at line 458270 (Claude.ai MCP initialization, contains "tengu_claudeai_mcp_eligibility")

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

The build it came inv2.1.14

20 Jan 2026 · 13 entries, this one is #7.

Either side of it

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.
envENABLE_CLAUDEAI_MCP_SERVERS
Eval sandboxes force claude.ai MCP servers off so they can't reach real servers.
flagtengu_claudeai_mcp_eligibility
An analytics event, not a feature flag. Claude Code logs it while deciding whether to load claude.ai MCP connectors, with a state field: disabled_env_var, disabled_setting, safe_mode, third_party_provider, api_key_precedence, no_oauth_token, missing_scope, eligible after the server list is fetched, or fetch_failed with the HTTP status and the number of attempts.

Is this right?