Repository navigation
MCP servers #27771
Description
Description
Bug Report
Local stdio MCP servers are completely non-functional on OpenCode Desktop for Windows. Remote MCPs work fine.
Environment
- OS: Windows 11
- OpenCode Desktop version: v1.15.0
- Node.js: v24.11.1 (installed via official installer)
- Installation method: Official Windows installer from opencode.ai
Current Behavior
All local MCP servers show red status in the Desktop app. Only remote MCPs (e.g., context7) show green and work correctly.
Specifically affected:
github(@modelcontextprotocol/server-github)agentmemory(@agentmemory/mcp)supabase(@supabase/mcp-server-supabase)- Any other local stdio MCP
Remote MCP that works:
context7(https://mcp.context7.com/mcp) → ✅ green
Expected Behavior
Local MCP servers should initialize and show green status, as they do on macOS and in the CLI version.
Steps to Reproduce
- Install OpenCode Desktop on Windows 11
- Add any local MCP to
opencode.jsonc(example: github) - Restart OpenCode Desktop
- Check MCP status — all local MCPs are red
What I've Already Tried
- ✅ Verified token is valid (GitHub API responds correctly)
- ✅ Tested
npx -y @modelcontextprotocol/server-githubdirectly in terminal — works fine standalone - ✅ Tried absolute path to
npx.cmdinstead ofnpx - ✅ Tried
cmd /c npx ...andpowershell -Command "npx ..." - ✅ Increased timeout to 60 seconds
- ✅ Pre-installed packages globally
- ✅ Created HTTP proxy wrapping stdio MCP (Streamable HTTP transport) — proxy responds correctly to JSON-RPC initialize request, but Desktop still shows red
- ✅ Confirmed config is in correct location (
%APPDATA%\opencode\opencode.jsonc) - ✅ Created
.jsoncopy alongside.jsonc - ✅ Cleared cache and restarted Desktop multiple times
Key Finding
The stdio MCP servers work perfectly when started manually outside OpenCode, but fail only when launched by OpenCode Desktop's internal process manager. Remote MCPs work fine.
Related Issues
- MCP Subsystem entirely unresponsive on Windows Desktop App (/config loads, but /mcp times out) #16449 — MCP Subsystem entirely unresponsive on Windows Desktop App
- fix(desktop): health check fails during server startup causing IDE instability #24142 — Health check fails during server startup
- MCP server processes accumulate across workspace switches and task delegations, causing sidecar hang #23882 — MCP server processes accumulate across workspace switches
Request
Is there a known workaround for Windows Desktop users, or an ETA for the fix? The CLI version works fine with local MCPs, so this appears to be Desktop-specific.
Logs
No error logs visible in standard locations. Happy to provide any additional diagnostics needed.
Plugins
context-mode
OpenCode version
1.15.0
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Activity
github-actions commentedon May 15, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct from these (e.g. a different root cause or regression in a newer version), please clarify how it differs so maintainers can track it separately.
rasos commentedon Jun 4, 2026
Local MCPs are not recognized or listed either on Linux. The MCP process is running and connected via sockets but not showing up in the GUI and it is not invoked when asking e.g. to index a directory. This seems to be a desktop app MCP issue, I can access the MCP with external scripts. Here is my config snippet:
Related to #30600 which was fixed lately.
github-actions commentedon Aug 4, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.