trovex for Roo Code
Roo Code supports remote streamable-HTTP MCP servers natively. Point it at trovex and the agent gets one canonical doc per query, about 60% fewer tokens.
Start trovex, then add it to Roo's mcp_settings.json (via the MCP panel) as a streamable-HTTP server:
{
"mcpServers": {
"trovex": {
"type": "streamable-http",
"url": "http://localhost:8765/mcp"
}
}
}
trovex is in private beta — request access first; the steps below work once you're in.
Setup, step by step
- Index your repo.$ uv run trovex index /path/to/repo
- Start trovex. It serves MCP over HTTP at
http://localhost:8765/mcp.$ uv run trovex serve - Open Roo's MCP settings and add the snippet above to
mcp_settings.json. Roo accepts thestreamable-httptransport with aurl(no command/args needed for a remote server). - Enable it. Toggle trovex on in the MCP panel; its
trovextool is now available to the agent.
Roo's MCP transport fields move between releases — if it doesn't connect, check Roo Code's current MCP transport docs.
Why Roo Code users want it
Roo reads files directly, which is exactly what burns tokens when project knowledge is spread across many markdown docs. trovex gives Roo the one canonical doc that answers a query — section-level, with a freshness marker — so it stops opening several files to find the current one. About 60% fewer tokens per lookup, plus a shared write path so what Roo learns is saved once and read back.
Give Roo Code one source of truth.
trovex is in private beta — request access, then index your repo and add the server.
Open source (AGPL-3.0 core, MIT CLIs). Local-first — your docs never leave your machine.