Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.274 ·

First-party MCP auto-auth fallback narrowed to design servers requiring consent

Automatic MCP re-authentication using a stored design token now only applies to /v1/design/ server URLs, not other first-party servers

Under the hood Improvements
JSON All of v2.1.274
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
What

For first-party MCP (Model Context Protocol, the system Claude Code uses to talk to external tool servers) servers, Claude Code previously had a fallback that could automatically re-authenticate using a consent-gated callback for any first-party-looking server. Now that fallback only fires when the server's URL is https, first-party, and its path starts with /v1/design/. A separate check for what counts as a matching first-party URL was also widened to include a new /v1/claude/test/ path, but the actual token-fallback behavior still only applies to /v1/design/ URLs.

Why

This narrows automatic authentication so that other first-party MCP servers no longer silently pick up a stored design-related credential; only design servers get that fallback now.

Gate state

No sentence about tengu_mcp_first_party_auto_auth since nothing has been read about it yet.

See this entry in the whole of v2.1.274 →

Feedback