Roo-Code: MCP servers not showing
App Version
3.9.0+
API Provider
OpenAI Compatible
Model Used
o3-mini
Actual vs. Expected Behavior
When using Roo versions bellow 3.9.0, I can edit the MCP json and the UI updates accordingly: from 3.8.6:
However, on versions 3.9.0 and above, the MCP section becomes blank, even with the same configuration:
from 3.9.0:
This happens with mcp-Atlassian, the brave MCP, and this (bogus) test configuration.
As far as I can tell, the MCPs themselves are also not functional in this state. Attempting to have Roo do something that would be serviced by a tool provided in the MCP results in Roo performing something else (EX: with mcp-Atlassian configured and asking it to read a jira issue TEST-123 causes it to instead try to read project files) As far as I can tell, this is not just a visual bug. But I’m kind of configuring the MCP in the dark, so what do i know 🤣
Detailed Steps to Reproduce
- On Roo 3.9.0 or above
- Navigate to MCP settings
- Enter in any MCP settings, even if they are bogus (or use the standard brave config everyone uses…)
- Save
- Observe that the MCP config is not recognized or shown in the MCP Settings pane
- Downgrade Roo to 3.8.6
- Reload extensions
- Navigate to MCP settings
- Observe that the MCP is now shown.
- Upgrade to Roo 3.9.0
- Reload extensions
- Navigate to MCP settings
- Observe that the MCP config is not recognized or shown in the MCP Settings pane
The only variable being changed in testing is the Roo version AFAIK. 3.9.0 also has release notes showing MCP logic was changed with that release to add SSE support, providing credence to the assumption that this is a bug.
Relevant API Request Output
Additional Context
Windows 11
VSCode versioning info: Version: 1.98.2 (user setup) Commit: ddc367ed5c8936efe395cffeec279b04ffd7db78 Date: 2025-03-12T13:32:45.399Z Electron: 34.2.0 ElectronBuildId: 11161602 Chromium: 132.0.6834.196 Node.js: 20.18.2 V8: 13.2.152.36-electron.0 OS: Windows_NT x64 10.0.22631
Any version of Roo code above 3.8.6 (I.E., 3.9.0 and above) appears to break MCP.
Versions tested: 3.8.4: working✅ 3.8.6: working✅ 3.9.0: not functional❌ 3.10.0: not functional❌ 3.10.5: not functional❌
Additionally, if I intentionally malform the JSON and save, I do get errors from Roo code. It seems that it at least reads the file in some fashion and that hook is working.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 5
- Comments: 22
My current workaround for MPC servers using the global MCP file. Works great for everything I have tried except Firecrawl.
Instead of:
As a windows 10 user this format works much better for me:
Even I’m also getting the issue, despite using mac, I’m using version 3.10.5
Thank you kind internet stranger, this fixed my issue with not being able to get Roo to detect MCP’s on Win11.