{"version":"2.1.274","anchor":"mcp-oauth-token-fallback-now-requires-a-design-server-url-ma","canonical_anchor":"mcp-oauth-token-fallback-now-requires-a-design-server-url-ma","heading":"MCP OAuth-token fallback now requires a design-server URL match","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/mcp-oauth-token-fallback-now-requires-a-design-server-url-ma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### MCP OAuth-token fallback now requires a design-server URL match\n\nMCP OAuth-token reuse now also requires the server's URL to match design-connector rules\n\n**What**\n\nWhen Claude Code decides whether an SSE or HTTP MCP (Model Context Protocol) server can skip its own OAuth check because a suitable access token already exists, it now also requires that server's URL to match the design-connector check before falling back to a generic OAuth probe.\n\n**Why**\n\nThis narrows when an existing access token can be reused to satisfy an MCP server's authentication, tying that shortcut specifically to design-connector servers rather than any server with a token available.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}