Unclear It does not say which MCP servers count as the app's own, so it is unclear whether a server you added yourself could ever be treated this way.
What
MCP servers are outside programs that give Claude Code extra tools. Claude Code now leaves some of them out when it tells the model which servers failed or need you to sign in.
- The summary the model gets while waiting for MCP servers to start now filters entries out of its "failed" and "needs authentication" lists. When some were left out, an extra note says so. Before, every failed and needs-auth server was listed.
- MCP servers that belong to the host app itself are now hidden this way. If one fails, disconnects or needs sign-in, the model gets fixed instructions instead. It is told not to name the server, not to ask you to reconnect or sign in, and to say that something went wrong on the app's end.
- These app-owned servers are also left out of other hidden reminders to the model, including the one about deferred tool search, a way of loading tools only when they are needed, and the one about servers that need authentication.
- Sign-in-again, step-up and connection errors for these servers are replaced with the same fixed text.
Before, app-owned servers were treated like any other server, with advice to reconnect through /mcp.
Why
When the tool server built into the app you are using breaks, you are no longer asked to reconnect or sign in to something you cannot fix yourself. You are told the problem is on the app's side. Ordinary MCP servers you added still come with /mcp advice.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It does not say which MCP servers count as the app's own, so it is unclear whether a server you added yourself could ever be treated this…