Claude Code v2.1.247 · 26 Aug 2026
MCP servers that fail to connect are now reported by default
MCP servers that fail to connect are now reported to you by default.
You'll notice Tier: how much it should matter to you
4 Useful: my rating, 1 to 5
2 Signal: worth watching, 1 to 5
MCP Area: what it touches
New Features Kind: in v2.1.247, 26 Aug 26
What probably matters to you Section of the release
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.
Read from
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
See this entry in the whole of v2.1.247 →
26 Aug 2026 · 298 entries, this one is #56.
Use it now22 You'll notice152 Nothing to try yet27 Under the hood97
Open the release →
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 55 of 298
Ctrl+letter works on non-Latin and alternate keyboard layouts
You'll notice Terminal Input
In v2.1.247 What probably matters to you release-page order
Next → · 57 of 298
Prompts typed mid-turn are checked by prompt-submit hooks at Enter
You'll notice Hooks