Skip to content

Gemini CLI lexvibe generate_policies

How to: Gemini CLI lexvibe generate_policies

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

Add lexvibe to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "lexvibe": {
      "httpUrl": "https://golexvibe.com/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something generate_policies does. Gemini CLI lists the server's tools on connect and calls generate_policies itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that lexvibe'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

lexvibe will not start until these are set, so generate_policies never becomes available.

  • LEXVIBE_APP_ID
  • LEXVIBE_API_URL
  • LEXVIBE_CDN_URL
  • LEXVIBE_EVENTS_URL
  • LEXVIBE_TELEMETRY

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.