{"version":"2.1.222","anchor":"claude-ai-mcp-proxy-surfaces-a-rejected-session-token","canonical_anchor":"claude-ai-mcp-proxy-surfaces-a-rejected-session-token","heading":"claude.ai MCP proxy surfaces a rejected session token","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/claude-ai-mcp-proxy-surfaces-a-rejected-session-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### claude.ai MCP proxy surfaces a rejected session token\n\nWhen your claude.ai session token is rejected, you now get a clear error telling you to run \/login.\n\n**What**\n\nA 401 from the claude.ai proxy that a token refresh cannot fix now becomes a typed error telling you to run \/login, instead of silently returning the original failed response.\n\n**Details**\n\n- error code CLAUDEAI_BEARER_REJECTED, recognised by connect, tools\/list, prompts\/get and skills\/list\n- sets `discoveryBearerRejected` on the client and skips the usual \"degraded\" telemetry\n- emits mcp_connect_claudeai_bearer_rejected and mcp_reconnect_bearer_rejected\n- the failed entry is evicted from the connection cache so a later attempt retries\n\n**Evidence**\n\n`claude.ai rejected the session token \u2014 it may lack connector scopes or be invalid. Run \/login.`\n\n- Area: MCP\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}