Claude Code / AI Coding Tools

Claude Code MCP OAuth DCR Re-run Orphaning Client IDs

Fix Claude Code MCP OAuth authentication loop where Dynamic Client Registration (DCR) runs repeatedly instead of reusing cached credentials, causing orphaned client IDs and stale refresh tokens Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 20, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 20, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token is a Claude Code failure pattern reported for developers trying to fix claude code mcp oauth authentication loop where dynamic client registration (dcr) runs repeatedly instead of reusing cached credentials, causing orphaned client ids and stale refresh tokens. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #59460 on anthropics/claude-code opened May 16 2026 by aria-inboxia. Labels: area:auth, area:mcp, bug, has repro, platform:macos. Open with 2 comments. Regresses authentication flows for users integrating MCP servers via OAuth. Directly impacts paid Claude Code Max plan users who rely on MCP integrations.

Common causes

GitHub Issue #59460 on anthropics/claude-code opened May 16 2026 by aria-inboxia. Labels: area:auth, area:mcp, bug, has repro, platform:macos. Open with 2 comments. Regresses authentication flows for users integrating MCP servers via OAuth. Directly impacts paid Claude Code Max plan users who rely on MCP integrations.

Quick fixes

Confirm the exact error signature matches MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token.
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token mean in Claude Code?

MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token indicates the workflow described by "Claude Code MCP OAuth DCR Re-run Orphaning Client IDs" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token?

Check whether this cause matches your environment: GitHub Issue #59460 on anthropics/claude-code opened May 16 2026 by aria-inboxia. Labels: area:auth, area:mcp, bug, has repro, platform:macos. Open with 2 comments. Regresses authentication flows for users integrating MCP servers via OAuth. Directly impacts paid Claude Code Max plan users who rely on MCP integrations.

Is the MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token guidance source-backed?

The "Claude Code MCP OAuth DCR Re-run Orphaning Client IDs" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token?

For "Claude Code MCP OAuth DCR Re-run Orphaning Client IDs", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging MCP OAuth: Claude Code re-runs DCR on every authenticate, orphaning the previously-issued client_id and its refresh_token?

For "Claude Code MCP OAuth DCR Re-run Orphaning Client IDs", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.