Claude Code / AI Coding Tools

Claude Code fails connecting to MCP servers without Dynamic Client Registration — OAuth flow aborts with 403

Fix Claude Code MCP connection failure with OAuth providers (Auth0, AWS Cognito, Okta) that do not support RFC 7591 Dynamic Client Registration — find workaround or permanent fix for OAuth auth flow Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 30, 2026 3 sources Needs local verification

Category: AI Coding Tools
Error signature: Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 30, 2026
Verification status: Source-backed
Evidence: 3 public source URLs

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

Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway is a Claude Code failure pattern reported for developers trying to fix claude code mcp connection failure with oauth providers (auth0, aws cognito, okta) that do not support rfc 7591 dynamic client registration — find workaround or permanent fix for oauth auth flow. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #3273 on anthropics/claude-code: 52+ 👍 reactions, ongoing discussion as of May 2026. Root cause: Claude Code forces DCR (RFC 7591) even when .mcp.json declares clientId; DCR fails 404/403 for Cognito/Auth0. Fixed as resolved in v2.1.30 via --client-id flag. Still highly searched because many users haven't upgraded or use custom plugin MCP servers (Cowork/GitHub plugin) that lack clientId plumbing.

Common causes

GitHub Issue #3273 on anthropics/claude-code: 52+ 👍 reactions, ongoing discussion as of May 2026. Root cause: Claude Code forces DCR (RFC 7591) even when .mcp.json declares clientId; DCR fails 404/403 for Cognito/Auth0. Fixed as resolved in v2.1.30 via --client-id flag. Still highly searched because many users haven't upgraded or use custom plugin MCP servers (Cowork/GitHub plugin) that lack clientId plumbing.

Quick fixes

Confirm the exact error signature matches Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway.
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 Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway 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 Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway mean in Claude Code?

Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway indicates the workflow described by "Claude Code fails connecting to MCP servers without Dynamic Client Registration — OAuth flow aborts with 403" 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 Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway?

Check whether this cause matches your environment: GitHub Issue #3273 on anthropics/claude-code: 52+ 👍 reactions, ongoing discussion as of May 2026. Root cause: Claude Code forces DCR (RFC 7591) even when .mcp.json declares clientId; DCR fails 404/403 for Cognito/Auth0. Fixed as resolved in v2.1.30 via --client-id flag. Still highly searched because many users haven't upgraded or use custom plugin MCP servers (Cowork/GitHub plugin) that lack clientId plumbing.

Is the Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway guidance source-backed?

The "Claude Code fails connecting to MCP servers without Dynamic Client Registration — OAuth flow aborts with 403" page is labeled source-backed. It has 3 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway?

For "Claude Code fails connecting to MCP servers without Dynamic Client Registration — OAuth flow aborts with 403", 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 Dynamic client registration failed: HTTP 403 / No client info found / Claude Code ignores configured oauth.clientId in .mcp.json and attempts DCR anyway?

For "Claude Code fails connecting to MCP servers without Dynamic Client Registration — OAuth flow aborts with 403", 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.