Prerequisites
- Roo Code extension for VS Code — search "Roo Code" in marketplace
- Node.js 18+
- Agent MCP Studio at agentmcp.studio
Step-by-Step Setup
Get your relay URL
Open the studio → Settings → MCP Relay Bridge → copy URL → click Connect.
Download bridge.js
curl -O https://agentmcp.studio/bridge.js && npm install ws
-
Configure MCP in Roo Code settings
Click the Roo Code icon in VS Code's sidebar → MCP Servers tab → Edit MCP Settings. Add:
{ "mcpServers": { "agent-mcp-studio": { "command": "node", "args": [ "/path/to/bridge.js", "wss://agentmcp.studio/api/relay/YOUR-UUID" ], "disabled": false, "autoApprove": [] } } }Roo Code uses the same MCP config format as Cline — if you already have Cline configured, the settings file is shared.
Use tools in any agent mode
Open a Roo Code task in Code or Architect mode. Type a request that uses your tools — Roo Code will call them automatically and show you the result before proceeding.
Both use identical MCP config. Roo Code adds extra agent modes (Architect for planning, Debug for troubleshooting) and some UX improvements. Try both — the config is compatible either way.
Frequently Asked Questions
Roo Code (formerly Roo Cline) is a powerful open-source AI coding agent for VS Code. It fully supports MCP — configure servers in the MCP Servers panel in the Roo Code sidebar and your tools appear immediately.
Yes — Roo Code is a fork of Cline with additional features like custom modes, boomerang tasks, and enhanced agentic capabilities. Both use the same MCP server configuration format, so Agent MCP Studio works identically with both.
Click the server icon in the Roo Code sidebar → MCP Servers → Add Server. Enter node as the command and add your bridge.js path and relay URL as arguments. Roo Code connects instantly without restarting VS Code.
Yes — Roo Code's Boomerang task orchestration can invoke MCP tools across subtasks. Your browser-built Agent MCP Studio tools are available to all Roo Code modes including Architect, Code, Ask, and custom modes.
Most common issues: Node.js not in PATH, wrong absolute path to bridge.js, UUID mismatch in the server config, or Studio not connected (click Connect in Settings tab first). Check the MCP server status indicator in the Roo Code panel.