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

> Use your real Chrome login state as an API: bb-browser provides a CLI + MCP server with 103 commands across 36 platforms (Twitter/Reddit/YouTube/etc.).

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
npm install -g bb-browser
bb-browser site update
bb-browser site zhihu/hot --json | head
# MCP: configure server as `npx -y bb-browser --mcp` (see README).
```

## Intro

Use your real Chrome login state as an API: bb-browser provides a CLI + MCP server with 103 commands across 36 platforms (Twitter/Reddit/YouTube/etc.).

**Best for:** Agents that need real web access (behind logins) without re-auth, API keys, or brittle scrapers

**Works with:** Node.js 18+, your real Chrome profile/login state, and MCP clients that can run stdio servers

**Setup time:** 8-20 minutes

### Key facts (verified)

- GitHub: 5133 stars · 506 forks · pushed 2026-05-11.
- License: MIT · owner avatar + repo URL verified via GitHub API.
- README-backed entrypoint: `bb-browser site update`.

## 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.

## Source & Thanks

> Source: https://github.com/epiral/bb-browser
> License: MIT
> GitHub stars: 5133 · forks: 506

---

<!-- ZH -->

## Quick Use

```bash
npm install -g bb-browser
bb-browser site update
bb-browser site zhihu/hot --json | head
# MCP: configure server as `npx -y bb-browser --mcp` (see README).
```

## Intro

bb-browser 把你的真实浏览器登录态当作 API：提供 CLI + MCP server，覆盖 36 个平台共 103 条命令；支持 daemon(默认 127.0.0.1:19824)、network 捕获与 --json/--jq 输出，适合给 agent 做网页工具层。

**Best for:** 需要访问“登录后网页能力”的 agent：不想反复登录、不想配 API key、也不想写脆弱爬虫

**Works with:** Node.js 18+、你的真实 Chrome 登录态，以及能运行 stdio MCP server 的客户端

**Setup time:** 8-20 minutes

### Key facts (verified)

- GitHub：5133 stars · 506 forks；最近更新 2026-05-11。
- 许可证：MIT；作者头像与仓库链接均已通过 GitHub API 复核。
- README 中可对照的入口：`bb-browser site update`。

## Main

- 把适配器当作代码：先用 `bb-browser site update` 拉取社区适配器；当某条流程进入生产关键路径后再做版本固定。

- 尽量用结构化输出：README 指出命令普遍支持 `--json` 与 `--jq`，更利于 agent 稳定消费与控 token 成本。

- 守住 daemon 边界：README 说明 daemon 默认绑定 127.0.0.1:19824；除非明确需求，不要暴露到不可信网络。

### Source-backed notes

- README 给出安装方式：`npm install -g bb-browser`，并通过 `bb-browser site update` 更新适配器。
- README 写明覆盖 36 个平台共 103 条命令，并由社区 `bb-sites` 提供适配器。
- README 记录 daemon 默认绑定 127.0.0.1:19824，并提供 `npx -y bb-browser --mcp` 的 MCP 配置示例。

### FAQ

- **需要 API key 吗？**：README 的核心思路是复用真实浏览器登录态；很多场景不需要额外 API key。
- **能当 MCP server 用吗？**：可以。README 提供 JSON 配置：运行 `npx -y bb-browser --mcp`。
- **把 daemon 暴露到外网安全吗？**：要谨慎。建议保持默认 localhost 绑定；如需远程请放在 VPN 等受控网络并做好审计。

## Source & Thanks

> Source: https://github.com/epiral/bb-browser
> License: MIT
> GitHub stars: 5133 · forks: 506


---
Source: https://tokrepo.com/en/workflows/bb-browser-browser-as-api-cli-mcp-server
Author: MCP Hub