Gemini CLI byte protocol byte_check_subscription

How to: Gemini CLI byte protocol byte_check_subscription

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

Add byte protocol to Gemini CLI

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

{
  "mcpServers": {
    "byte-protocol": {
      "httpUrl": "https://mcp.payperbyte.io/mcp"
    }
  }
}

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

byte protocol will not start until these are set, so byte_check_subscription never becomes available.

PRIVATE_KEY
RPC_URL
BYTE_GATEWAY_ATTESTER

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.

byte protocol MCP server