Agent Update

Connect

Gemini CLI → Agent Update

Google's open-source terminal agent for Gemini, configured through a settings.json in ~/.gemini.

Gemini CLI talks to Agent Update over MCP. The server is https://api.tryagentupdate.com/v1/mcp, the transport is Streamable HTTP, and the credential is one header.

Where it goes: ~/.gemini/settings.json (user) or .gemini/settings.json (project)

Setup

~/.gemini/settings.json
{
  "mcpServers": {
    "agent-update": {
      "httpUrl": "https://api.tryagentupdate.com/v1/mcp",
      "headers": { "Authorization": "Bearer au_live_..." },
      "timeout": 30000
    }
  }
}
Or from the CLI
gemini mcp add --transport http --scope user agent-update \
  https://api.tryagentupdate.com/v1/mcp --header "Authorization: Bearer au_live_..."

Before you file a bug

--scope defaults to project, not user. The bare command writes ./.gemini/settings.json, and it hard-errors if you run it from $HOME. httpUrl means Streamable HTTP; a plain url means SSE-or-HTTP. The CLI itself writes {url, type:"http", headers} rather than httpUrl, and both forms work. timeout is milliseconds. Server definitions belong under mcpServers, not the separate top-level mcp object. Don't set oauth or authProviderType.

Check it worked

Ask the agent to text you. A 401 means the token is wrong, or the word Bearer is in there twice. No tool at all means the transport string is wrong. Both are covered in troubleshooting.

Next

The five tools and their arguments are on the MCP page. The same tools over plain HTTP are on the REST page. Every other tool is on the docs index.

← All docs