Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

MCP OAuth stops sending a client id that only works for loopback

You'll notice
Useful4 Signal2
MCP

MCP OAuth stops sending a client id that only works for loopback, and repairs saved entries.

What

Both MCP OAuth providers now withhold the metadata-document URL as the client id whenever the redirect URI is not that document's loopback /callback address, falling back to a configured client or dynamic registration instead. A saved client entry holding a stale metadata URL as its client id is repaired in place.

Details
  • MCP_OAUTH_CLIENT_METADATA_URL still overrides which document URL is used.
Evidence

stale CIMD client_id repair

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.242 →