Claude Code now shows a persistent notification when an MCP server's automatic reconnection attempts run out
Claude Code connects to MCP servers (external tool providers that plug into Claude Code) and tries to reconnect automatically if a server disconnects. If those automatic reconnection attempts run out without success, a persistent notification now appears telling you to reconnect manually by running /mcp. The notification clears on its own once the server successfully connects again.
Previously a server could sit disconnected without a clear signal that automatic retries had given up. This notification makes it obvious when manual action is needed, and points directly at /mcp to fix it.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
With `"oauth": true`, Claude Desktop registers its own public client through dynamic client registration and lists this URI as the client's only redirect URI, so the authorization server must offer a registration endpoint and accept an `ht…third-party/claude-desktop/extensions see the edit
| Provider credentials, API keys, bearer tokens, and MCP secrets | **No**, except the client secret of a Google Desktop-app OAuth client, which Google doesn't treat as confidential. You can enter one for [Google sign-in to your provider](#…third-party/claude-desktop/admin-console see the edit
Anthropic's documentation has since written up /mcp, on Deploy with Enterprise Admin Console.
Added a notification when an MCP server disconnects mid-session and automatic reconnection gives up, pointing at /mcp