Gemini CLI leafwright leafwright_login

How to: Gemini CLI leafwright leafwright_login

client:Gemini CLI transport:streamable-http tool:leafwright_login

Add leafwright to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "leafwright": {
      "httpUrl": "https://leafwright.co/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something leafwright_login does. Gemini CLI lists the server's tools on connect and calls leafwright_login itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that leafwright's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

leafwright will not start until these are set, so leafwright_login never becomes available.

LEAFWRIGHT_API_KEY
LEAFWRIGHT_MCP_TOKEN
LEAFWRIGHT_PROJECT_ID
LEAFWRIGHT_MCP_READ_ONLY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

leafwright MCP server