trovex Compare Answers Setup Request access

trovex for Windsurf

Windsurf keeps MCP servers in ~/.codeium/windsurf/mcp_config.json and manages them from Cascade. Add trovex and the agent gets one canonical doc per query — about 60% fewer tokens.

The config

Start trovex, then add it to ~/.codeium/windsurf/mcp_config.json using serverUrl for the streamable HTTP endpoint:

{
  "mcpServers": {
    "trovex": { "serverUrl": "http://localhost:8765/mcp" }
  }
}

trovex is in private beta — request access first; the steps below work once you're in.

Setup, step by step

  1. Index your repo.
    $ uv run trovex index /path/to/repo
  2. Start trovex. It serves MCP over HTTP at http://localhost:8765/mcp.
    $ uv run trovex serve
  3. Edit ~/.codeium/windsurf/mcp_config.json (on Windows, %USERPROFILE%\.codeium\windsurf\mcp_config.json) — the snippet above.
  4. Refresh. Open Cascade → MCP / Plugins and refresh. The trovex tool is now available.

Older Windsurf builds connect to HTTP servers through the mcp-remote bridge instead of serverUrl. If trovex doesn't appear, check Windsurf's current MCP docs for the format your version expects.

Why Windsurf users want it

Cascade is strong at navigating code, but for project knowledge spread across many markdown files it still rereads to find the current one. trovex serves the single canonical doc that answers, with a freshness marker, so Cascade reads the right section instead of a stale copy — about 60% fewer tokens per lookup, with a shared write path so context carries across sessions.

Give Windsurf one source of truth.

Index your repo, start trovex, edit mcp_config.json — about a minute.

Open source. No cloud, no API keys. Your docs never leave your machine.