bb-browser — Browser-as-API CLI + MCP Server

Main

• Treat adapters as code: update from community (bb-browser site update), then pin versions when a workflow becomes production-critical.

• Use structured output: most commands support --json and --jq so your agent can consume stable, token-efficient payloads.

• Secure the daemon boundary: README states the daemon binds to 127.0.0.1:19824 by default; keep it local unless you know why you need remote access.

Source-backed notes

• README shows installing via npm install -g bb-browser and updating adapters via bb-browser site update.
• README states there are 103 commands across 36 platforms, powered by the community bb-sites repo.
• README documents a daemon default bind of 127.0.0.1:19824 and an MCP config snippet using npx -y bb-browser --mcp.

FAQ

• Do I need API keys?: The README positions it as using your real browser login state; many commands work without separate API keys.
• Can I run it as an MCP server?: Yes. README includes a JSON MCP config snippet that runs npx -y bb-browser --mcp.
• Is it safe to expose the daemon remotely?: Be cautious. Start with the default localhost bind; remote access should be protected (e.g., VPN) and audited.