{"version":"2.1.321","anchor":"mcp-oauth-issuer-is-stored-with-the-client","canonical_anchor":"mcp-oauth-issuer-is-stored-with-the-client","heading":"MCP sign-in now saves which sign-in server issued the client","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-oauth-issuer-is-stored-with-the-client","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### MCP sign-in now saves which sign-in server issued the client\n\nWhen an MCP server has no `oauth.clientId` set, Claude Code now saves the sign-in server's issuer along with the client\n\n**What**\n\nSome MCP servers, outside programs that give Claude extra tools, need you to sign in through OAuth, a standard sign-in flow. When Claude Code saves the sign-in details for such a server and the server's settings have no `oauth.clientId`, it now also saves the issuer: the identity of the sign-in server it found while setting up.\n\n**Why**\n\nThis affects signing in again to MCP servers that do not name a client in their settings.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}