Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Gemini CLI

BuildBase in your AI tools: connect Gemini CLI to BuildBase's own MCP server and manage your BuildBase organization from Gemini CLI. You sign in as yourself, and Gemini CLI can do only what your role and your organization allow.

Add BuildBase to Gemini CLI

The address is the same in every AI tool: https://api.console.buildbase.app/mcp. BuildBase signs you in the first time Gemini CLI connects.

  1. In Gemini CLI, add a remote MCP server: gemini mcp add, or settings.json. Use the address https://api.console.buildbase.app/mcp, or the command or config below.
  2. Sign in: run /mcp auth buildbase-console. Gemini CLI finds the sign-in from the server's first answer and opens a browser. It needs a browser on the same machine, so it does not sign in over SSH without port forwarding.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Gemini CLI and what it asks for.
  4. Ask Gemini CLI something, such as "List my BuildBase organizations."
terminalBash
gemini mcp add --transport http buildbase-console https://api.console.buildbase.app/mcp
settings.jsonJSON
{
  "mcpServers": {
    "buildbase-console": {
      "httpUrl": "https://api.console.buildbase.app/mcp"
    }
  }
}

The plan it needs

Gemini CLI's MCP page does not name a plan. Its documentation says Antigravity CLI replaced it on 18 June 2026 for unpaid and Google One users.

How sign-in looks in Gemini CLI

Gemini CLI finds the sign-in from the server's first answer and opens a browser. It needs a browser on the same machine, so it does not sign in over SSH without port forwarding.

What is different in Gemini CLI

  • includeTools and excludeTools choose the tools (excludeTools wins). trust: true skips every confirmation, so leave it off for a server that can change things.
  • BuildBase adds its own rules on top: each organization is Off, Read only or Read and change for AI agents (Read only by default), and deletes, member and role changes, sends and money moves need your approval in the chat.
  • For a job with nobody to sign in, send one of your organization's API keys as the bearer instead. Add --header "Authorization: Bearer <key>" to gemini mcp add.

If it does not work in Gemini CLI

Gemini CLI needs to sign in again
Run /mcp auth <name>.
Gemini CLI does not connect
/mcp and gemini mcp list show each server's state; --debug opens the debug console. In settings.json, httpUrl is Streamable HTTP and url is the older SSE transport.
Gemini CLI says the organization does not let agents in
An owner or admin sets the organization's AI agents setting in the console, under Account, then Security. Off turns every agent away, and an owner or admin can also block one agent for one member there.
Gemini CLI cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Gemini CLI can then make changes without signing in again. Deleting, sending to an audience, roles and money still ask you to approve each change.

Frequently Asked Questions

Which Gemini CLI plan do I need?

Gemini CLI's MCP page does not name a plan. Its documentation says Antigravity CLI replaced it on 18 June 2026 for unpaid and Google One users.

Can Gemini CLI change things in my BuildBase organization?

Only where the organization allows it: Read only is the default. Even then, deletes, member and role changes, sends and money moves need your approval in the chat, and secrets never reach Gemini CLI.

Can I connect Gemini CLI with an API key instead of signing in?

Yes, for a job with nobody to sign in: send one of your organization's API keys as the bearer. Add --header "Authorization: Bearer <key>" to gemini mcp add. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next