Integrations / AI agent clients / Goose
A browser extension for Goose.
Goose extends itself with MCP servers it calls extensions. Add Browz as one and Goose can open, read and act on real pages in isolated profiles, from the desktop app or the terminal.
/Applications/Browz.app/Contents/Resources/browz-mcpSetup
Set it up.
Install Browz and open it
Download Browz; the MCP server ships inside it.
Add it with goose configure
Choose Add Extension, then Command-line Extension. Name it
browz, give the command below, keep the default timeout and add no environment variables.Command/Applications/Browz.app/Contents/Resources/browz-mcpOr edit config.yaml
Add the extension under
extensionsin~/.config/goose/config.yaml(on Windows,%APPDATA%\Block\goose\config\config.yaml).config.yamlextensions: browz: name: browz type: stdio cmd: /Applications/Browz.app/Contents/Resources/browz-mcp args: [] enabled: true envs: {} timeout: 300Or try it for one session
Start Goose with the extension for this session only, without changing your config.
Terminalgoose session --with-extension "/Applications/Browz.app/Contents/Resources/browz-mcp"
Config format from Goose: using extensions, Goose config files.
Example
A daily check that keeps its sign-in.
A persistent session comes back with the same profile, cookies and proxy every day, so Goose stays signed in to the dashboard you check.
Using Browz, open a persistent session with identity "dashboard/daily", go to https://dashboard.example.com, and if it asks me to sign in, stop and tell me. Otherwise take a screenshot of the summary panel and close the session.The first time, sign in yourself in the profile’s window; later runs reuse the same profile and its cookies.
Good to know
Notes and tips.
- The snippets use the macOS path of the server inside Browz. On Windows it is
%LOCALAPPDATA%\Programs\Browz\browz-mcp.exe, on Linux/usr/lib/browz/browz-mcp; or usenpx -y @browz/mcp, which finds it. - The remote server at
https://mcp.gobrowz.com/mcpis in free public beta: it needs the Browz app open with Remote control on, on a computer with a hardware security chip, and offers the profile, tab and page tools. See what it needs and what it offers. - Browz has to be installed and open on the same computer: the local MCP server drives the app’s own profiles through its local API, and reads the app’s credentials itself, so no token goes in the config.
- A person completes sign-ins, 2FA codes and CAPTCHAs. The agent can pause with
browz_request_humanand hand you the profile’s window, then carry on in the same session. Browz never solves or bypasses CAPTCHAs. - Use agents only where each site’s terms allow automated use, on accounts you are entitled to use. Our acceptable use policy applies to agents the same as to people.
- The MCP server is on every plan, Free included (5 profiles). How many agent sessions can be open at once depends on the plan: see pricing.
FAQ
Goose and Browz.
Does it work in Goose Desktop and the CLI?
Yes. Both read the same config.yaml, so an extension added in one shows in the other.
What is the timeout for?
It is how long, in seconds, Goose waits for one call to the extension. Page loads usually take a few seconds, so 300 leaves plenty of room.
Can Goose use the hosted server?
Goose supports remote extensions over Streamable HTTP and signs you in, so it can reach the hosted server in beta. The local extension above needs nothing else and keeps everything on your computer.
Get started
Download Browz. Every task, its own browser.
curl -fsSL https://gobrowz.com/agents/install.sh | sh