Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.307 ·

Clearer advice when an MCP server won't let Claude Code sign in

When an MCP server rejects Claude Code's automatic sign-in registration, Claude Code now suggests concrete next steps instead of a bare error

You'll notice Improvements
JSON All of v2.1.307
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.307,
ImprovementsSection of the release

Unclear It is not clear whether this advice is shown to every user or only under certain conditions.

What

MCP 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:

  • Connect to the service through a claude.ai connector instead.
  • Ask an admin for help.
  • 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.
Why

Before, 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether this advice is shown to every user or only under certain conditions.

See this entry in the whole of v2.1.307 →

Feedback