Gemini CLI openstates mcp server openstates_search_events

How to: Gemini CLI openstates mcp server openstates_search_events

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

Add openstates mcp server to Gemini CLI

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

{
  "mcpServers": {
    "openstates-mcp-server": {
      "httpUrl": "https://openstates.caseyjhand.com/mcp"
    }
  }
}

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

openstates mcp server will not start until these are set, so openstates_search_events never becomes available.

OPENSTATES_API_KEY
OPENSTATES_DAILY_REQUEST_BUDGET
OPENSTATES_REQUEST_TIMEOUT_MS
OPENSTATES_TOTAL_REQUEST_BUDGET_MS
MCP_LOG_LEVEL

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.

openstates mcp server MCP server