Roo Code (formerly Roo Cline) is an AI coding assistant VS Code extension that evolved from the Cline codebase with additional features for autonomous task execution. Its MCP config format is very similar to Cline: it uses the mcpServers root key and adds alwaysAllow and disabled to each server entry. One notable difference for remote servers is that Roo Code requires an explicit type field and uses streamable-http where the canonical format uses http. Roo Code also supports additional server options like watchPaths and disabledTools for fine-grained control. The config lives in VS Code's extension storage for the rooveterinaryinc.roo-cline extension, separate from Cline's storage, so you can run both extensions with independent server lists.
Quick Install with getmcp
The fastest way to install MCP servers in Roo Code is with the getmcp CLI:
•VS Code installed (version 1.85 or higher recommended)
•Roo Code extension installed from the VS Code Marketplace (rooveterinaryinc.roo-cline)
•An AI model API key configured in Roo Code settings
•Node.js 18 or higher for running npx-based servers
Popular Servers for Roo Code
Troubleshooting
▸Config file not found: Roo Code creates its config directory after the first install and VS Code restart. Open VS Code with Roo Code installed, then add servers.
▸Remote server type mismatch: Roo Code requires type: streamable-http for streamable HTTP servers — it does not accept the bare http value. The getmcp CLI handles this mapping; manual edits must use the correct value.
▸Conflict with Cline: Roo Code and Cline store configs in separate directories (different extension IDs). Having both installed is fine, but you need to add servers to each separately.
▸Server not appearing in the Roo Code panel: After editing the config file directly, use the Roo Code MCP settings panel in VS Code to reload. Sometimes a full VS Code window reload (Ctrl+Shift+P > Developer: Reload Window) is needed.
