bb-browser MCP Server

Content

bb-browser is a browser-control CLI and MCP server for AI agents. It connects agents to a real Chrome session through a local daemon and browser extension, so the agent can inspect pages, use site adapters, capture screenshots, evaluate page JavaScript, inspect network traffic, and call authenticated browser fetches with the active user's login state.

The project positions the browser itself as the API. That makes it powerful for sites without public APIs, but also means the agent can interact with real accounts and logged-in pages.

Source Review

• https://github.com/epiral/bb-browser
• https://github.com/epiral/bb-browser/blob/main/README.md
• https://github.com/epiral/bb-browser/blob/main/PRIVACY.md
• https://github.com/epiral/bb-browser/blob/main/package.json
• https://registry.npmjs.org/bb-browser
• https://github.com/epiral/bb-sites

These sources were reviewed on 2026-06-06. Prefer the live repository, README, privacy document, package metadata, npm registry metadata, and community adapter repository for current MCP configuration, daemon behavior, site commands, privacy claims, and adapter coverage.

Features

• Run an MCP server with npx -y bb-browser --mcp.
• Control a real Chrome session through a local daemon and extension.
• Use site adapters for search, social, news, developer, video, finance, jobs, knowledge, shopping, and tool workflows.
• Inspect DOM snapshots and accessibility trees.
• Click elements, fill inputs, evaluate JavaScript, and open pages.
• Capture screenshots and network request data.
• Fetch URLs using the browser's authenticated session.
• Use OpenClaw mode for supported browser workflows without the Chrome extension.
• Update and recommend community site adapters.

Installation

Configure bb-browser in an MCP client:

{
  "mcpServers": {
    "bb-browser": {
      "command": "npx",
      "args": ["-y", "bb-browser", "--mcp"]
    }
  }
}

Follow the upstream README for the daemon, Chrome extension, OpenClaw path, and site adapter setup. Start with read-only commands such as page inspection, search, or summaries before enabling page actions.

Use Cases

• Let an agent inspect a logged-in page without separate API credentials.
• Search or summarize data from websites that do not provide useful public APIs.
• Capture page structure, screenshots, console output, and network context for debugging.
• Use community adapters for social, developer, finance, video, job, and knowledge sites.
• Build new site adapters from observed browser network and DOM behavior.

Safety and Privacy

bb-browser can act through a real browser session. Treat every command as if it could use the privileges of the logged-in human. Keep the daemon local, use non-critical accounts for experiments, and require approval before any command that posts, submits, purchases, deletes, changes settings, or sends messages.

The upstream privacy document says bb-browser communication is local and does not send telemetry or data to an external service. That does not make tool outputs automatically safe for models. DOM text, screenshots, network bodies, authenticated fetch results, and adapter output can still be sent to the MCP client and model provider.

Duplicate Check

No epiral/bb-browser entry, bb-browser MCP entry, or matching source URL was found in content/mcp.