Connect Goose

Add looot as a remote Streamable HTTP extension in Goose, in the desktop app or the CLI.

Goose is Block’s open-source agent. It calls MCP servers extensions. A remote one is a “Remote Extension (Streamable HTTP)”.

Before you start you need a looot account. The runs you make spend the organization’s balance, so top up before your first paid run. See Before your first run.

Steps

1. Desktop: open Settings, Extensions and click Add custom extension. Set the type to Streamable HTTP, the name to looot, and the endpoint to https://api.looot.ai/mcp.
2. CLI: run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP). Enter the name looot and the endpoint https://api.looot.ai/mcp.
3. Start a session with the extension enabled.

The server URL is https://api.looot.ai/mcp.

Sign-in

Goose’s extension docs show a URL and optional headers, not a browser sign-in. If the server answers 401, create an agent token in Settings and add it as an Authorization: Bearer <token> header in the extension, or bridge the sign-in with mcp-remote. Keep the token out of shared config.

Check it works

Ask Goose to call balance or catalog_overview. Both are free. A working connection answers with your available balance, or the catalog’s categories and job counts.

A first prompt to try

Ask looot for my balance, then search its catalog for a tool that finds a work email from a name and company domain, and show me the price before running anything.

Troubleshooting

• Timeout on slow runs: raise the extension timeout (the CLI prompt asks for one).
• Wrong type: choose Streamable HTTP, not SSE.
• Extension off: enable it for the session in Settings, Extensions.
• Still stuck: see Troubleshooting.

What you see when you connect

If the client uses browser sign-in, it opens looot.ai and shows the consent page: which organization to bill, which scopes to grant and how long to stay connected. See The consent page.

Sources

• Using extensions: goose-docs.ai/docs/getting-started/using-extensions