The /mcp view now counts cached servers separately so you can tell them from live connections.
tengu_mcp_discovery_cache Not enough to sayNothing 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.221: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.221. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Cached MCP servers are now counted and reported as their own state in the inline /mcp summary, the MCP dialog, and the SDK wait-for-servers result.
- The inline
/mcpsummary line counts cached servers separately, assembling a string containing the fixed fragment${A} cached,. - The dialog status mapper returns
"cached"for cached entries. - The control/SDK "wait for MCP servers" result schema gained an optional
cached: w.array(w.string()).optional()list alongside connected, failed, stillPending, needsAuth and disabled. - Only meaningful on the MCP discovery cache path (tengu_mcp_discovery_cache); without cached entries the counts read as before.
if (Yt.type === "cached") return "cached";
Strings lifted out of the shipped bundle, so the claim above can be checked against them.