Gemini CLI ainpc cli ainpc_get_started

How to: Gemini CLI ainpc cli ainpc_get_started

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

Add ainpc cli to Gemini CLI

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

{
  "mcpServers": {
    "ainpc-cli": {
      "httpUrl": "https://mcp.ainpcengine.com/mcp"
    }
  }
}

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

ainpc cli will not start until these are set, so ainpc_get_started never becomes available.

AINPC_API_KEY
AINPC_GAME_ID

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.

ainpc cli MCP server