{"version":"2.1.307","anchor":"mcp-guidance-when-a-server-rejects-dynamic-client-registrat","canonical_anchor":"mcp-guidance-when-a-server-rejects-dynamic-client-registrat","heading":"Clearer advice when an MCP server won't let Claude Code sign in","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/mcp-guidance-when-a-server-rejects-dynamic-client-registrat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Clearer advice when an MCP server won't let Claude Code sign in\n\nWhen an MCP server rejects Claude Code's automatic sign-in registration, Claude Code now suggests concrete next steps instead of a bare error\n\n**Unclear.** It is not clear whether this advice is shown to every user or only under certain conditions.\n\n**What**\n\nMCP servers are add-ons that give Claude a set of extra tools. Some of them ask you to sign in, and Claude Code normally registers itself with the service automatically during that sign-in, a step called dynamic client registration. Some services refuse that step. When one does, Claude Code now tells you that this service doesn't accept sign-ins from Claude Code and suggests a next step that fits your situation:\n\n- Connect to the service through a claude.ai connector instead.\n\n- Ask an admin for help.\n\n- Register an app with the service yourself, using the redirect URL `http:\/\/localhost:<port>\/callback`, then add the server again with `--client-id`, `--callback-port` and `--client-secret`.\n\n**Why**\n\nBefore, a refused sign-in left you with an unclear OAuth error (OAuth is the standard sign-in method these servers use). Now you get a concrete way forward.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}