Connecting Cursor

Veri connects Cursor's CLI agent (cursor-agent) through a project-scoped .cursor/mcp.json. This page documents exactly what gets written, where, and how to verify it works. Using a different agent? See Claude Code, Codex CLI, or Gemini CLI.

What Veri writes

Open a work order in Veri and click Start agent session. The roster lists every agent detected on your machine; if Cursor's row says mcp config: veri entry missing, click Set up & launch. Veri writes .cursor/mcp.json inside the project root — the directory that contains veri/, which is where Cursor looks for project-scoped MCP config:

{
  "mcpServers": {
    "veri": {
      "command": "node",
      "args": [
        "/Applications/Veri.app/Contents/Resources/app/node_modules/@veri/mcp/dist/server.js",
        "/Users/you/code/your-project"
      ]
    }
  }
}

• command: "node" — Cursor launches the server with your own Node (version 20 or newer). This keeps the file portable — no machine-specific runtime path baked into something you may commit and share.
• First argument — the MCP server script that ships inside the Veri app. The path contains no version segment, so it stays valid across app self-updates.
• Second argument — the project root the server serves: the folder containing veri/.

Veri detects Cursor by finding cursor-agent on your shell's PATH. If Cursor's row says not detected on this machine, install the Cursor CLI first (in Cursor: the command palette's "Install CLI" action), then reopen the picker.

Restart your agent

Agents read MCP config on launch. Set up & launch starts a fresh cursor-agent session in Terminal after writing the file, so the config is picked up. For sessions you start yourself, launch cursor-agent from the project folder after the file exists — an already-running session won't see a config written mid-flight.

Verify it works

Two sides to prove. The server side: Veri's connection screen (Settings → Agent connection) has LIVE CHECK → Verify connection, which launches the server with a real MCP handshake and a search call proving it serves this project — the same script and project root Cursor's config points at. The agent side: in a Cursor agent session, ask it to search the veri knowledge base — a working connection answers with your project's documents through the veri tools rather than by grepping files.

What the agent gets

The same ten tools every connected agent gets — get_context, get_import_instructions, search, get_document, get_neighbors, file_decision, file_work_order, file_requirement, file_source, file_receipt — detailed in the tool table on the Claude Code page.