Bumblebeez

Bumblebeez documentation

What Bumblebeez is

Bumblebeez gives an AI assistant a temporary cloud browser, powered by BrowserBox. Your assistant starts a browser, opens pages, reads them, clicks and types, retrieves files, and ends the browser. A person can open a viewer link to the same browser to sign in or take over. Bumblebeez does not provide an AI model; you use the assistant you already have.

Bumblebeez is early access and offered for business use by people 13 or older (see the Service terms). Connect the MCP URL below as a custom connector in Claude or ChatGPT, sign in with your email code, and add $5 at billing. Your assistant can then start a browser; open its viewer link to watch or take over.

Connect it

The remote MCP server is:

https://agents.browserbox.io/oauth/mcp

It uses Streamable HTTP with OAuth. The authorization server is https://auth.agents.browserbox.io.

In Claude

  1. On claude.ai, open Settings, then Connectors, and add a custom connector with the URL above (or install Bumblebeez from the Claude connector directory once it is listed).
  2. Choose Connect. You are sent to the Bumblebeez sign-in page, then a consent page that lists what the connection can do. Approve it.
  3. In a chat, enable the connector and ask, for example, “Start a Bumblebeez browser, open bumblebeez.ai/preview/orders, tell me the orders, then end the browser.”

In ChatGPT

  1. In ChatGPT, add Bumblebeez as an app or connector (from the app directory once listed, or as a custom MCP connector with the URL above where your plan allows it).
  2. Choose Connect, sign in with your email; you get a code by mail, and approve consent.
  3. Ask ChatGPT to use Bumblebeez to start a browser and perform your task.

In Grok Build

  1. Install the plugin and add the server: grok mcp add --transport http bumblebeez https://agents.browserbox.io/oauth/mcp.
  2. Open /mcps, select bumblebeez, and press i to sign in. Ask for a task on a site you are authorized to use, and end the session when finished.

Sign in

Sign-in happens on our issuer at auth.agents.browserbox.io using the standard OAuth authorization-code flow with PKCE. Your assistant receives a token for your account only; it never sees your password. Every browser belongs to the account that created it, and tools only see browsers owned by the signed-in account. Do not put passwords or tokens in chat messages or support email.

The eight tools

ToolWhat it does
browser_createAllocates one light cloud browser for up to 15 minutes. Takes a request_id (reusing it with the same options returns the existing session) and ttl_minutes (1 to 15).
browser_listLists the cloud browsers owned by the connected account.
browser_inspectRead-only. Returns the current page, tables, links, forms, controls, status, tabs or frames, without navigating or interacting.
browser_interactNavigates and interacts using Grip actions: go, back, forward, reload, do, type, press, hover, focus, reveal, scroll, tab and frame. It can change the browser and the website you are on.
browser_accessCreates a viewer link so a person can join the same browser, for example to sign in or take over.
browser_downloadsLists downloads that are ready in the browser.
browser_downloadRetrieves one ready download (up to 4 MiB) and returns its bytes and SHA-256. The download is consumed.
browser_endEnds the browser and waits for the provider to confirm it has stopped. This can take longer than a minute.

A typical run: browser_create, browser_interact (go to a page), browser_inspect, optionally browser_downloads and browser_download, then browser_end. Always end the browser when you are done.

Pricing

Usage is metered per browser minute against a prepaid balance on your account. In the current configuration the rate is 1 cent per minute. A new account gets 25 cents of starter credit once per email address at first sign-in; that covers one full browser request and expires after 30 days, and no card is needed to try. After that, browsers are billed from prepaid credit at 1 cent a minute. The sandbox used for directory review runs in payment test mode, so no real card is charged there. Prices and included usage for paid access are stated in the Order we agree with you, and the Order controls (see Service terms, section 6).

Limits

Because the browser can reach public websites, you are responsible for the sites you direct it to and for following their rules and our acceptable use terms. Take over the browser yourself for logins, purchases, submissions and other consequential steps.

Data handling

Pages, form data and files you or your assistant process in a browser are Customer Data. Browser workspaces are temporary and follow the session lifecycle. If you ask a tool to return a result, your AI provider may receive page content or file bytes, and it handles them under its own terms. Retrieve any file you need before ending the session. We do not sell personal information and do not use browser content to train general-purpose AI models. Details are in the Privacy notice and the Service terms. Do not use the Service for regulated data such as protected health information without a written agreement.

Try it without an account

A sample page for testing, bumblebeez.ai/preview/orders, lists three sample orders and offers a small CSV download. A walkthrough recorded in Claude shows a full start, read and end run.

Support

Email sales@dosaygo.com with your AI client, what you tried, and when. Redact passwords, tokens and session links. See Support for security reports.