Repository navigation
MCP server failed to start (unstable MCP servers) #829
Description
I have a problem with my Playwright MCP. The connection is not stable enough so during the opencode startup, it fails to connect.
In Claude Code, it worked by trying to connect later and succeeding, but it seems like opencode gives up.
I can't really reproduce this consistently, but what I do is configure MCPs in opencode.json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"playwright": {
"type": "remote",
"url": "http://localhost:8900/mcp",
"enabled": true
}
}
}Then start opencode, and ask it to navigate to some website, like this: https://opencode.ai/s/0Yigi01r.
Then, I start the Playwright MCP server with npx @playwright/mcp@latest --port 8900 --headless --isolated and try prompting again without closing opencode. It doesn't connect.
A workaround that works for me is to use some kind of MCP proxy
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"playwright": {
"type": "local",
"command": ["mcp-proxy", "http://localhost:8900/mcp"],
"enabled": true
}
}
}https://opencode.ai/s/tPnQZCgZ
Basically, I asked it to navigate to a website, and the request just hung until it timed out (couldn't interrupt btw.). But when I started the MCP, it worked immediately without having to restart opencode.
That proxy was initially built for Tidewave (Elixir MCP), but it seems to work well with other MCPs too.
https://github.com/tidewave-ai/mcp_proxy_rust
https://elixirdrops.net/d/UAo4BtYi
Activity
moesmufti commentedon Jul 14, 2025
same issue +1
edit: I get this constantly now, not just on 'unstable' connections. Server is definitely running but it shows the error upon any new session
clouatre commentedon Sep 14, 2025
Proxy Stability Comparison: mcp-remote vs mcp-proxy
Our enterprise testing confirms your observation about proxy reliability differences.
mcp-remote Experience:
mcp-proxy Assessment:
Enterprise Impact: Both proxies have architectural limitations that affect production deployments:
Reference Implementation: Claude Code's native SSE transport eliminates proxy layer entirely, providing better stability and simpler debugging.
Recommendation: While mcp-proxy may be more stable for specific use cases, native SSE + OAuth implementation (issue #988) would eliminate proxy dependency and associated stability concerns entirely.
feat(mcp): add auto-reconnection for MCP servers
rekram1-node commentedon Dec 28, 2025
[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!