Skip to content

Gemini CLI Dropspace approve_autopilot_draft

How to: Gemini CLI Dropspace approve_autopilot_draft

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

Add Dropspace to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "dropspace": {
      "httpUrl": "https://api.dropspace.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

Dropspace will not start until these are set, so approve_autopilot_draft never becomes available.

  • DROPSPACE_API_KEY
  • DROPSPACE_API_URL

Same tool, other clients

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