Gemini CLI LienDeadline list_state_lien_guides

How to: Gemini CLI LienDeadline list_state_lien_guides

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

Add LienDeadline to Gemini CLI

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

{
  "mcpServers": {
    "liendeadline-mcp": {
      "httpUrl": "https://mcp.liendeadline.com/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something list_state_lien_guides does. Gemini CLI lists the server's tools on connect and calls list_state_lien_guides itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that LienDeadline'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

LienDeadline will not start until these are set, so list_state_lien_guides never becomes available.

LIENDEADLINE_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 4 October 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.

LienDeadline MCP server