Skip to content
BuildBase
Agent-ready apps

Let your users connect Goose to your app

Agent-ready apps: make the app you build with the SDK ready for Goose. Your users add your app's MCP server to Goose, sign in on your hosted page and approve it, and Goose acts as them, never as more.

How your users add your app to Goose

Give your users your app's MCP address. npx buildbase agent install --url <your MCP address> prints the setup for each AI tool, Goose included, with your address filled in.

  1. In Goose, your user adds a remote MCP server: goose configure > Add Extension > Remote Extension (Streamable HTTP). They use your app's MCP address, https://app.example.com/api/mcp in these examples.
  2. Sign in. Goose gets a client by itself the first time and signs you in in the browser.
  3. Your hosted sign-in page opens. Your user signs in and approves the consent screen, which names Goose and what it asks for.
  4. Goose can now use your tools, as that user and with that user's permissions.

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 runs on your user's own computer, so it reaches any address that computer can, including a development server while you test.
  • Your server's built-in tools are read-only until you allow changes. Goose's extensions page does not document per-tool controls for a remote extension.
  • goose session --with-streamable-http-extension "<url>" adds it for one session only.

If it does not work in Goose

Goose cannot register or sign in
Turn on Let agents register themselves, with a base client, in the console under Authentication, then Agent readiness. Goose registers its own client the first time it connects.
Goose does not connect
Choose Remote Extension (Streamable HTTP) as the type; the other types are for local or older servers.
Check your server the way Goose will
Run npx buildbase agent doctor --url <your MCP address>. It walks the first contact a client makes (the sign-in challenge, the metadata, redirects, a stable tool list) and exits 1 when a check fails.

Frequently Asked Questions

Which Goose plan do your users need?

Goose's documentation does not name a plan.

Does my MCP server need to be public for Goose?

No. Goose runs on your user's computer, so it reaches what that computer reaches. Your users still need an address they can open, and production should be public HTTPS.

Can Goose change data in my app?

Only through tools you allow, and only as the user who connected it. The built-in tools are read-only by default, and a tool that needs extra scopes is hidden until the user grants them.

Where next