Connecting Gemini CLI

Veri connects Gemini CLI (gemini) through a project-scoped .gemini/settings.json. This page documents exactly what gets written, where, and how to verify it works. Using a different agent? See Claude Code, Cursor, or Codex 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 Gemini CLI's row says mcp config: veri entry missing, click Set up & launch. Veri writes the veri server entry into .gemini/settings.json inside the project root — the directory that contains veri/, which is where Gemini CLI looks for project-scoped settings:

{
  "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" — Gemini CLI 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/.

If your project already has a .gemini/settings.json with other settings, Veri adds only the mcpServers.veri entry and leaves everything else in the file as it was.

Restart your agent

Agents read MCP config on launch. Set up & launch starts a fresh gemini session in Terminal after writing the file, so the config is picked up. For sessions you start yourself, launch gemini 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 Gemini's config points at. The agent side: in a Gemini CLI 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.