{"version":"2.1.229","anchor":"mcp-oauth-no-longer-re-saves-a-stale-client-secret-or-redire","canonical_anchor":"mcp-oauth-no-longer-re-saves-a-stale-client-secret-or-redire","heading":"MCP OAuth no longer re-saves a stale client secret or redirect URI","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/mcp-oauth-no-longer-re-saves-a-stale-client-secret-or-redire","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### MCP OAuth no longer re-saves a stale client secret or redirect URI\n\nMCP sign-in no longer saves a stale client secret or redirect address back to disk.\n\n**What**\n\nSaving OAuth client details for an MCP server now drops the client secret when the issuer is known, the client id matches the one already stored with no secret against it, and it matches the configured `oauth.clientId`. A previously stored redirect URI is only reused when this client is not doing the redirect itself, instead of falling back to the current one.\n\n**Details**\n\n- Prevents a secret from a different registration being written back over a secretless entry.\n\n**Evidence**\n\n`mcpOAuth`\n\n- Area: MCP\n- Names: `oauth.clientId`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}