Source Intelligence

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.247 Home All releases olderv2.1.246 v2.1.248newer
Claude Code v2.1.247

MCP servers that fail to connect are now reported by default

You'll notice
Useful4 Signal2
MCP

MCP servers that fail to connect are now reported to you by default.

Feature flag
tengu_surface_failed_mcp_servers Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.247: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.247. It isn't a statement about your account. What a flag value here can and cannot tell you

What

The switch controlling whether MCP servers that failed to connect are shown to you now defaults to on instead of off, so unless the server says otherwise you will see connection failures reported.

Details
  • The gate is tengu_surface_failed_mcp_servers; only its local fallback changed, from false to true.
  • A server-supplied value still wins over the fallback.
Evidence

tengu_surface_failed_mcp_servers

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.247 →