Configuration

Configuration

Cursor

Add the Arxo MCP server to .cursor/mcp.json (or your MCP config file):

{
  "mcpServers": {
    "arxo": {
      "command": "/path/to/arxo-mcp",
      "args": ["--cache-ttl", "300"],
      "env": {}
    }
  }
}

• command — Full path to the arxo-mcp binary. If the workspace is the Arxo repo, use "${workspaceFolder}/target/release/arxo-mcp". On Windows, use backslashes: "${workspaceFolder}\\target\\release\\arxo-mcp.exe".
• args (optional) — Server arguments; see Server arguments below.
• env (optional) — Environment variables; see Environment variables below.

Cursor workspace path

For single-root workspaces, project_path: "." in tool calls refers to the workspace folder. For multi-root workspaces, use the absolute path to the project you want to analyze.

Claude Desktop and other MCP clients

Configure the MCP server with:

• Command — Path to the arxo-mcp binary
• Args (optional) — --cache-ttl <seconds>, --max-cache-entries <n>, --log-level <level>
• Transport — stdio (default); the server uses stdin/stdout for JSON-RPC

Server arguments

Argument	Description
--cache-ttl <seconds>	Cache TTL in seconds (default: 300).
--max-cache-entries <n>	Maximum number of cached analysis results (default: 512000).
--log-level <level>	Log level (e.g. debug, info). You can also set RUST_LOG to override.

Logs go to stderr so they do not interfere with the JSON-RPC stream on stdout.

Environment variables

Variable	Purpose	Example
RUST_LOG	Log level (overrides --log-level)	arxo_mcp=debug
ARCH0_ENGINE_PATH	Path to the Arxo engine binary (if not bundled)	/path/to/arxo-engine

Set these in the env block of your MCP config:

{
  "mcpServers": {
    "arxo": {
      "command": "/path/to/arxo-mcp",
      "args": [],
      "env": {
        "RUST_LOG": "arxo_mcp=debug"
      }
    }
  }
}