Skip to content

Gemini CLI agentPickup cancel_pickup_order

How to: Gemini CLI agentPickup cancel_pickup_order

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

Add agentPickup to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "agentpickup": {
      "httpUrl": "https://agentpickup.app/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

agentPickup will not start until these are set, so cancel_pickup_order never becomes available.

  • AGENTPICKUP_SHOP_URL
  • AGENTPICKUP_WALLET_KEY
  • AGENTPICKUP_MAX_PER_ORDER
  • AGENTPICKUP_NETWORKS
  • AGENTPICKUP_DIRECTORY_URL

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.