[BUG] Desktop: "Could not connect to MCP server" errors for mcp-registry and Claude in Chrome on app restart
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
On Claude Desktop restart, two toast error notifications appear:
- "Could not connect to MCP server mcp-registry"
- "Could not connect to MCP server Claude in Chrome"
Chat functionality appears unaffected, but the errors persist across every restart. Other MCP servers (e.g., PowerShell.MCP v1.7.0) connect successfully — only mcp-registry and Claude in Chrome fail.
The Claude in Chrome MCP bridge also fails programmatically — tools that depend on it return "No tab available" or "No browser responded within the timeout" even when the extension is installed, authorized, and showing its sidebar panel.
What Should Happen?
MCP servers should connect without errors on startup, or auto-retry silently until connected.
Error Messages/Logs
Toast notification 1: "Could not connect to MCP server mcp-registry"
Toast notification 2: "Could not connect to MCP server Claude in Chrome"
MCP bridge programmatic errors:
- "No tab available" (when attempting tool calls after connection)
- "No browser responded within the timeout. Make sure Chrome is open with the Claude extension installed, then try again." (switch_browser tool)
- "Multiple Chrome extensions connected" (when extension installed on both Chrome Beta and Edge Beta)
- Extension disconnects mid-session: "Claude in Chrome Extension Disconnected - The connection to Claude in Chrome was lost"
Steps to Reproduce
- Close Claude Desktop completely
- Reopen Claude Desktop v1.1.3963
- Navigate to any Chat
- Observe two red toast error notifications
- (Optional) Attempt to use Claude in Chrome MCP tools — they fail with connection errors
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
N/A — Claude Desktop v1.1.3963 (MSIX)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
- PowerShell.MCP v1.7.0 connects fine, suggesting the issue is specific to mcp-registry and Claude in Chrome, not the MCP framework itself.
- The Claude in Chrome extension is installed on Microsoft Edge Beta, not Chrome. The MCP bridge may only scan for chrome.exe processes. If Edge Beta isn't supported, the error message should say so rather than showing a generic connection failure.
- The MCP bridge connection is also unstable — it drops mid-session even after successful initial connection via the "Claude Desktop wants to connect" dialog.
- Environment: Windows 11 Pro 25H2 Build 26200
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗