Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Goose

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

Add BuildBase to Goose

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

  1. In Goose, add a remote MCP server: goose configure > Add Extension > Remote Extension (Streamable HTTP). Use the address https://api.console.buildbase.app/mcp.
  2. Sign in. Goose gets a client by itself the first time and signs you in in the browser.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Goose and what it asks for.
  4. Ask Goose something, such as "List my BuildBase organizations."

The plan it needs

Goose's documentation does not name a plan.

How sign-in looks in Goose

Goose gets a client by itself the first time and signs you in in the browser.

What is different in Goose

  • Goose's extensions page does not document per-tool controls for a remote extension.
  • 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.
  • goose session --with-streamable-http-extension "<url>" adds it for one session only.

If it does not work in Goose

Goose does not connect
Choose Remote Extension (Streamable HTTP) as the type; the other types are for local or older servers.
Goose 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.
Goose cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Goose 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 Goose plan do I need?

Goose's documentation does not name a plan.

Can Goose 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 Goose.

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

Goose's documentation does not describe sending a key, so sign in as yourself. That also keeps each change in the audit log under your name.

Where next