Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

MCP tool list refreshes avoid name clashes, and per-server overrides set ask-for-tools

Refreshed MCP tool lists are no longer applied when another server holds the name, and per-server permission overrides also set ask-for-tools

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

Unclear It is not clear what value mcpAskForTools takes when no per-server override has been set.

What

MCP servers (Model Context Protocol servers, add-ons that give Claude extra tools) can announce that their list of tools has changed. Claude Code then asks the server again for the list. When it receives the new list, Claude Code now looks up the server's current configuration. Previously it matched the list by server name alone. If another server now holds that name, Claude Code does not apply the new list, and it reports "A re-queried tool list was not applied: another server holds the name".

Separately, setting a permission override for a single server now also writes the mcpAskForTools setting. Previously only the override itself was saved.

Why

If servers were renamed or replaced while a refresh was in progress, a tool list could end up attached to the wrong server. That can no longer happen. Permission overrides for a server are now also tied to whether Claude Code asks before using that server's tools.

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 what value `mcpAskForTools` takes when no per-server override has been set.

See this entry in the whole of v2.1.290 →

Feedback