{"version":"2.1.251","anchor":"mcp-auth-now-tracks-which-kind-of-login-token-it-used","canonical_anchor":"mcp-auth-now-tracks-which-kind-of-login-token-it-used","heading":"MCP auth now tracks which kind of login token it used","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/mcp-auth-now-tracks-which-kind-of-login-token-it-used","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### MCP auth now tracks which kind of login token it used\n\nMCP connection failures now record which kind of login token was in play.\n\n**What**\n\nWhen Claude Code authenticates to a first-party MCP server, it now records whether the token came from a normal login or from a login carrying the Design connector's extra `user:design:read` scope. The kind of token last used is passed into connection-failure diagnostics, so a failure can be told apart by which credential was in play.\n\n**Details**\n\n- Which kind applies depends on whether your login has the `user:design:read` scope.\n\n**Evidence**\n\n`design_scoped_login`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}