Skip to content

Gemini CLI Spurvik spurvik_setup_snippet

How to: Gemini CLI Spurvik spurvik_setup_snippet

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

Add Spurvik to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "spurvik-mcp-server": {
      "httpUrl": "https://console.spurvik.com/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

Spurvik will not start until these are set, so spurvik_setup_snippet never becomes available.

  • SPURVIK_MCP_ROOT
  • SPURVIK_API_KEY
  • SPURVIK_HMAC_SECRET

Same tool, other clients

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