Claude Code / AI Coding Tools
Claude Code fails to connect to MCP servers without Dynamic Client Registration — Incompatible auth server error
Fix Claude Code OAuth/MCP connection failure when connecting to enterprise identity providers (Auth0, AWS Cognito) that don't support DCR Includes evidence for Claude Code troubleshooting demand.
- Category
- AI Coding Tools
- Error signature
Dynamic client registration failed: HTTP 403 / Error: Incompatible auth server: does not support dynamic client registration- Quick fix
- Verify the account session, API key, provider settings, and environment where the failing tool is running.
- Updated
What this error means
Dynamic client registration failed: HTTP 403 / Error: Incompatible auth server: does not support dynamic client registration is a Claude Code failure pattern reported for developers trying to fix claude code oauth/mcp connection failure when connecting to enterprise identity providers (auth0, aws cognito) that don’t support dcr. 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 repo with 52+ 👍 reactions, open since Jul 2025, last comment 10 hours ago (May 21, 2026). Multiple real-world production repros including AWS Cognito + PKCE. Claude Code strictly requires DCR per spec’s MAY clause, ignoring pre-registered clientId in .mcp.json. Covers GitHub MCP, Slack plugin, Cowork, and custom OAuth IdPs.
Common causes
- GitHub issue #3273 on anthropics/claude-code repo with 52+ 👍 reactions, open since Jul 2025, last comment 10 hours ago (May 21, 2026). Multiple real-world production repros including AWS Cognito + PKCE. Claude Code strictly requires DCR per spec’s MAY clause, ignoring pre-registered clientId in .mcp.json. Covers GitHub MCP, Slack plugin, Cowork, and custom OAuth IdPs.
Quick fixes
- Confirm the exact error signature matches
Dynamic client registration failed: HTTP 403 / Error: Incompatible auth server: does not support dynamic client registration. - 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.
Sources checked
Evidence note: GitHub issue #3273 on anthropics/claude-code repo with 52+ 👍 reactions, open since Jul 2025, last comment 10 hours ago (May 21, 2026). Multiple real-world production repros including AWS Cognito + PKCE. Claude Code strictly requires DCR per spec’s MAY clause, ignoring pre-registered clientId in .mcp.json. Covers GitHub MCP, Slack plugin, Cowork, and custom OAuth IdPs.
Related errors
- AI Coding Tools
FAQ
What should I check first?
Start with the exact Dynamic client registration failed: HTTP 403 / Error: Incompatible auth server: does not support dynamic client registration text and the smallest action that reproduces it.
Can I ignore this error?
No. Treat it as a failed Claude Code workflow until the root cause is understood.
Is this guaranteed to have one fix?
No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.
How do I know the fix worked?
Rerun the same command, editor action, or request. The fix is working when that action completes without Dynamic client registration failed: HTTP 403 / Error: Incompatible auth server: does not support dynamic client registration.