Skip to content

Gemini CLI Cuecaps studio_link

How to: Gemini CLI Cuecaps studio_link

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

Add Cuecaps to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "cuecaps-mcp": {
      "httpUrl": "https://cuecaps.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

Cuecaps will not start until these are set, so studio_link never becomes available.

  • CUECAPS_API_KEY
  • CUECAPS_CHROME

Same tool, other clients

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