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.299 ·

MCP servers can be marked failed before Claude Code tries to connect

When Claude Code refreshes MCP servers, a check before connecting can now mark a server as failed without trying to reach it

Under the hood Internal Changes
JSON All of v2.1.299
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.299,
Internal ChangesSection of the release

Unclear What the up-front check tests is not known, so which servers it marks as failed is unclear.

What

MCP servers are outside programs that give Claude Code extra tools. When your MCP configuration changes, Claude Code goes through the list of servers and brings them up to date. Before, it connected to each server directly.

Now a check runs on each server's configuration first. If the check fails, the server is marked as failed and Claude Code does not try to connect. The same check runs again after a connection is made. A list of extra servers is now also taken into account when deciding what is permitted.

Why

In practice a server can now show as failed without any connection attempt, so a failure is not always a network or server problem.

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 doubtWhat the up-front check tests is not known, so which servers it marks as failed is unclear.

See this entry in the whole of v2.1.299 →

Feedback