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.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Reconnecting an MCP server can discard its cached discovery

You'll notice
Useful3 Signal2
MCP

Reconnecting an MCP server can now throw away its cached tool list and rediscover everything.

/mcp
What

Claude Code caches the tool and prompt list an MCP server reports so it does not have to ask again. Reconnecting a server can now throw that cache away and rediscover from scratch, which the MCP management screen asks for when the server was not seen fresh. The cache itself is on by default and only turns off if a server-side kill switch value is set.

Details
  • A second reconnect path sits next to the normal one and is chosen when the caller asks to discard discovery and the existing connection was not itself a cached or still-pending entry.
  • That path also removes the stale cached entry, so the next connection repopulates it.
  • No local setting exposes the kill switch; the check reports the cache as live unless a value has been pushed.
Evidence

reconnectMcpServerDistrusted

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

See this entry in the whole of v2.1.238 →