Roo Code reads MCP configs from `.roo/mcp.json` in your project root. Project-level configs override global settings.
OVERVIEW
Roo Code is a VS Code extension with native MCP support. It reads from `.roo/mcp.json` (project-level) or the global `mcp_settings.json` (accessible via the MCP panel). Project configs take precedence. Roo Code auto-detects the file when it exists in your workspace root — no manual reload needed.
CONFIG FILE LOCATION
Create this file: .roo/mcp.json in your project root. Create the .roo directory if it does not exist.
Paste the JSON exactly as shown. The format is the same as Cursor and Cline.
Replace `mcp_sk_your_key_here` with the real key from Dashboard → API Keys.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}Or use the Roo Code MCP settings panel:
Verify the server loaded before using it.
Ensure `.roo/mcp.json` is in the workspace root (not a subdirectory). The file must be valid JSON with no trailing commas.
Check that `npx` is on your PATH. Try running `npx -y zephex` manually in your terminal. If it fails, Node.js is not properly installed.
Ensure "Enable MCP Servers" is checked in the Roo Code settings. If disabled, no MCP tools will load regardless of config.
Increase the Network Timeout for the server in the MCP panel. Default is 60 seconds — try 120 for slower connections or cold starts.
If the editor still does not connect, return to Quickstart or check Connection Issues.