{"version":"2.1.229","anchor":"mcp-oauth-repairs-a-stale-saved-client-instead-of-re-registe","canonical_anchor":"mcp-oauth-repairs-a-stale-saved-client-instead-of-re-registe","heading":"MCP OAuth repairs a stale saved client instead of re-registering","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/mcp-oauth-repairs-a-stale-saved-client-instead-of-re-registe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### MCP OAuth repairs a stale saved client instead of re-registering\n\nA stale saved OAuth client for an MCP server is repaired in place instead of re-registered.\n\n**What**\n\nWhen a saved OAuth client for an MCP server has an out-of-date redirect URI, Claude Code no longer always forces a fresh dynamic registration. If a client ID is configured, it updates the stored entry in place, adopting that client ID and clearing the secret, or just bringing the redirect URI into line, and uses it. Failures to write the repair are logged.\n\n**Evidence**\n\n`stale client_id repair`\n\n- Area: MCP\n- Names: `oauth.clientId`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}