BrowserDo

MCP浏览器工具

提供方 未标注

浏览器工具 stdio · 本地进程 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

为 AI 智能体打造,与人共享。Embiody 的 MCP 服务器,Embiody 是一款面向 AI 智能体的 Windows 浏览器:可在后台的真实标签页中读取页面、搜索、点击和输入,并可将标签页交给用户处理登录或验证码。

一句话选型结论

按资料字段整理

BrowserDo 属于浏览器工具类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类浏览器工具 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

浏览器工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

网页抓取

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
npx -y browserdo-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
自动操作网页

打开页面、点击、填表,把浏览器动作交给模型执行。

抓取结构化数据

把页面内容整理成表格或 JSON,省掉手工复制粘贴。

关键流程回归

按步骤检查页面是否正常,回归时少漏环节。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在浏览器工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
BrowserDo当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
Playwright MCP Server 21 stdio · 本地进程 本地部署 有 2026-05-18
Fetch 9a2682de 1 SSE · 服务端推送 支持远程部署 有 2026-05-18
Browser 738d52bc 未标注 stdio · 本地进程 本地部署 有 2026-05-17
MCP 40600ece 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Skyvern MCP 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

浏览器工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类浏览器工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

14.6 KB
来自项目仓库与上游目录的原文,未做删改

BrowserDo

Website: embiody.com/browserdo

Built for AI agents. Shared with people.

Embiody is a Windows browser your AI agent works in, in the background and
at full speed, while you keep using your PC and can step in at any time. BrowserDo is the
MCP server that connects your agent to it. Add it to Claude
Code, Claude Desktop, Codex, Cursor, VS Code or Gemini CLI, and your agent can browse, click, type
and read pages, including sites you are signed in to.

Why BrowserDo

Each point below has a short clip recorded on real sites. The side-by-side ones run the same task
at the same moment through Playwright MCP and BrowserDo, from one Claude Code session.

1. Works in the background at full speed, and leaves your screen to you

Chrome and Embiody countdowns in a background tab, behind a window and minimized. Click for the 38-second clip.

Pages run at full speed in background tabs, background windows, minimized windows and hidden
windows. Your agent does not need the browser in front of you, so you keep using your computer
while it works, and it can work in a dozen tabs at once.

Ordinary Chrome slows down pages you are not looking at. In our test, a browser window was
completely covered by another window for 7 minutes:

Timers A countdown on the page
Embiody, front tab 10 per second throughout on time
Embiody, background tab 10 per second throughout on time
Chrome, front tab slowed down after 12 seconds 355 seconds behind

No launch flags are needed for this. One limit: a page opened while its window is minimized
may come back without a screenshot; its text and element numbers are still there.

2. Works where bots get blocked — because it isn't one

Walmart, Target, adidas and realtor.com stop Playwright MCP with a bot check; Embiody goes straight through. Click for the 24-second clip.

Your agent works in your own browser, on your behalf, so sites with anti-bot protection treat it
the way they treat you. We also signed in to an account on a site protected by a leading
commercial bot-detection service, the kind that usually stops automation tools.

3. Sees the whole page and clicks the right thing

On nytimes.com a privacy overlay swallows Playwright MCP’s click; BrowserDo gives the agent only the overlay’s buttons, so it closes it first. Click for the 28-second clip.

  • Elements covered by a popup or overlay get no number, so the agent can't click something you
    can't see.
  • Content inside embedded frames from other sites, such as payment forms and sign-in boxes, can
    be read and clicked.
  • Long pages are read whole, not only the part on screen.
  • An element off screen is scrolled into view before it is clicked.
  • Clicks land where they should across multiple monitors and at any display scaling.
  • Every element number belongs to one snapshot. A number from an older snapshot is refused
    before anything is clicked, instead of hitting whatever took its place.

4. You can see what the agent is doing

The "AI-controlled tab" badge, then the highlighted border and the agent’s own cursor. Click for the 15-second clip.

A tab the agent is working in shows a virtual mouse pointer, a frame around the page and a
marker on the tab. Open it any time to watch.

5. You and the agent share one tab

Disputing a charge on Uber Help: the agent hands you the tab for the sign-in code, then takes it back. Click for the 38-second clip.

The agent fills in the forms; you step in for the sign-in code, the captcha or the payment, then
hand the tab back, and the agent picks up where you left off. If you click or type in a tab the
agent is working in, you are asked whether to take it over. The agent asks before it touches a
tab of yours.

6. Fewer tokens for the whole page

The browser engine itself boils each page down for the agent: its text, plus every element the
agent can act on, numbered. On Wikipedia, GitHub, CNN, ESPN and Apple, a whole-page snapshot took
37% of the tokens of Playwright MCP's (o200k tokenizer, same 1600×1000 viewport, November 2026),
and the agent can read just the screen it is working on.

7. Several steps in one call

Real speed: the agent fills 4 form fields in 2.5 seconds with one call. Click for the 3-second clip.

browser_batch runs several actions (clicks, typing, key presses) in a row and returns a fresh
snapshot of the page, so the agent needs fewer round trips and fewer tokens.

8. Reads the page itself, not a summary

A JB Hi-Fi search page: Claude Code’s built-in fetch gets a browser warning and 0 products; BrowserDo reads all 18 with prices. Click for the 30-second clip.

browser_read_pages returns the page's own text, links included, from pages built by scripts and
from sites you are signed in to. It can stand in for Claude Code's WebFetch, which fetches the page
without running its scripts and hands back a short model-written summary.

9. Sees the browser's own popups

McDonald’s store finder asks for your location: Playwright MCP’s agent never sees the prompt; BrowserDo reports it and the agent allows it once. Click for the 30-second clip.

Permission bubbles, menus, Save As dialogs, "Leave site?" prompts and alerts are reported in every
snapshot, with the ways each one can be answered.

10. Current engine, signed releases

Built on Chromium 156. The installer carries the digital signature of SELECTIOUS PTY LTD, which
BrowserDo verifies before running it, and the browser updates itself, checking the signature of
every update.

Requirements

  • Windows 10 or 11, 64-bit (Embiody is Windows only for now)
  • Node.js 20 or newer. Check with node -v. Without it, BrowserDo fails to start (Claude Code shows
    "Failed to connect"). Install it with winget install OpenJS.NodeJS.LTS, then restart your client.
  • The Embiody browser, version 0.9.0.3 or newer: installed automatically the first time BrowserDo
    starts. That is a download of about 140 MB and takes a few minutes; your client can use BrowserDo
    at once, and until the browser is ready each tool replies with the progress. With an older one, BrowserDo opens the browser's update page and asks you to restart
    the browser and BrowserDo once it has updated (details).

No API key is needed. Your agent drives the browser with its own model.

Install

BrowserDo runs as npx -y browserdo-mcp. Pick your client and follow only that section; the others
are for other clients.

Claude Code```bash

claude mcp add browserdo -- npx -y browserdo-mcp


Add `--scope project` to share it with your team through `.mcp.json`, or `--scope user` to use it
in every project.

### Claude Desktop

Edit `%APPDATA%\Claude\claude_desktop_config.json`:```json
{
  "mcpServers": {
    "browserdo": {
      "command": "npx",
      "args": ["-y", "browserdo-mcp"]
    }
  }
}

Codex```bash

codex mcp add browserdo -- npx -y browserdo-mcp


Or add to `~/.codex/config.toml`:```toml
[mcp_servers.browserdo]
command = "npx"
args = ["-y", "browserdo-mcp"]

Cursor

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):```json
{
"mcpServers": {
"browserdo": {
"type": "stdio",
"command": "npx",
"args": ["-y", "browserdo-mcp"]
}
}
}


### VS Code

Run **MCP: Add Server** from the Command Palette, choose **Command (stdio)** and enter
`npx -y browserdo-mcp`. Or add to `.vscode/mcp.json`:```json
{
  "servers": {
    "browserdo": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "browserdo-mcp"]
    }
  }
}

Gemini CLI

Add to ~/.gemini/settings.json (all projects) or .gemini/settings.json (one project):```json
{
"mcpServers": {
"browserdo": {
"command": "npx",
"args": ["-y", "browserdo-mcp"]
}
}
}


### Other MCP clients

Add a local (stdio) MCP server in your client's settings, with command `npx` and arguments
`-y browserdo-mcp`. Most clients take it in this shape:```json
{
  "mcpServers": {
    "browserdo": {
      "command": "npx",
      "args": ["-y", "browserdo-mcp"]
    }
  }
}

Then ask your agent to do something on the web:

> Find me a direct flight from Sydney to Melbourne next Wednesday morning and show me the
> three cheapest options.

Tools

Each tool is one browser action. windowId and tabId are optional everywhere; leave them out
and the frontmost window and tab are used.

Tool What it does
browser_take_snapshot The page as one line per element, each actionable element with a number, plus the page position, URL, title, any popups in the way and a snapshotId. Says when the page is a PDF, an error page or a crashed tab. includeImage adds the annotated screenshot; readWholePage reads beyond the screen.
browser_read_pages Read up to 10 pages at once in background tabs and get their text, with links as footnotes.
browser_batch Several actions on one tab in a row, then a fresh snapshot. Stops at the first failure, and after a step that changed the page.
browser_click, browser_input_text, browser_press_key, browser_select_editable_text, browser_scroll Act on an element by its number and the snapshotId it came from. browser_input_text can also edit at a place named by the surrounding words.
browser_move, browser_drag Hover; press, carry and release. Drag works sliders, canvases and reorderable lists.
browser_navigate, browser_go_back, browser_go_forward, browser_reload, browser_stop_loading, browser_wait Getting around.
browser_get_window_info, browser_new_window, browser_close_window, browser_show, browser_minimize Windows. browser_get_window_info lists every window and tab with their ids.
browser_new_tab, browser_select_tab, browser_close_tab, browser_set_audio_muted Tabs.
browser_close_popup_bubble Answer a permission bubble or dialog.
browser_start_human_control, browser_stop_human_control Hand the tab to a person for a password or captcha, then take it back.
browser_status Whether the browser is ready, or how far its first install has got.

Settings

Set these in the env block of your client's config, or put them in a config file (copy
browserdo.config.example.yaml to browserdo.config.yaml next to where the server runs, or pass
--config). Environment variables win over the config file.

Variable What it does
EMBIODY_TOOLS browser (the tools above), task (browser_run_task only) or all (default).
EMBIODY_SAVE_SNAPSHOTS 1 saves every snapshot's screenshots and page text under run/browser_data, for debugging. Off by default.
EMBIODY_EXE_PATH Launch your own Embiody build, on a separate profile, instead of the installed one.
EMBIODY_USER_DATA_DIR Give the agent a separate profile folder instead of your own Embiody; BrowserDo then starts a browser of its own on it.
EMBIODY_VLLM_ENDPOINT, EMBIODY_VLLM_MODEL, EMBIODY_VLLM_API_KEY The model for browser_run_task (below).

The example config file explains the rest: fallback models, timeouts, how long to let pages
settle. --transport sse serves MCP over HTTP at http://127.0.0.1:3000/sse instead of stdio; it
answers this machine only.

Privacy

BrowserDo has no telemetry, usage statistics or error reporting.

  • Downloads: the first time it starts without Embiody installed, it downloads the installer
    from GitHub, or from a mirror if GitHub can't be reached. The installer carries the digital
    signature of SELECTIOUS PTY LTD; BrowserDo checks it before running the installer and refuses
    one that is unsigned or signed by anyone else.
  • Updates: when your client starts BrowserDo with npx, npm checks the npm registry for the
    latest version when it starts BrowserDo. That request is made by npm, not by BrowserDo.
  • Your model: only browser_run_task sends anything to a model, and only to the endpoint you
    configure. The browser tools return pages to your own agent.
  • On your computer: a debug log at %LOCALAPPDATA%\Embiody\BrowserDo\logs records the URLs
    visited and the steps taken, never page content or your task. It keeps at most three 5 MB files.
    Snapshots are not saved unless you set EMBIODY_SAVE_SNAPSHOTS=1.
  • Your profile: the agent works in your own Embiody, in its Default profile, so it can use
    the sites you are signed in to there. Other Embiody profiles are not used, and neither are other
    browsers on your computer, such as Chrome or Edge. To keep the agent
    apart, set EMBIODY_USER_DATA_DIR to a folder of its own.

See the privacy policy and the
Embiody end-user license agreement.

Optional: browser_run_task

If you would rather hand over a whole task than drive the browser step by step,
browser_run_task runs it inside BrowserDo with a vision model of your choice (any
OpenAI-compatible endpoint), and keeps the screenshots out of your agent's context.```json
"env": {
"EMBIODY_VLLM_ENDPOINT": "<your-openai-compatible-endpoint>",
"EMBIODY_VLLM_MODEL": "<your-vision-model>",
"EMBIODY_VLLM_API_KEY": "<your-api-key>"
}


| Parameter | Notes |
| --- | --- |
| `task` | **Required.** The task, in plain language. |
| `windowId`, `tabId` | Pass both to continue an earlier task in the same tab. |
| `maxRounds` | Default 12. |
| `closeTabWhenDone`, `closeBrowserWindowWhenDone` | Default false. |
| `humanReply` | Your answer to the question a previous run stopped on, when your client can&#x27;t ask you mid-task. |

When the task needs you, it asks. A step only you can do, like a password or a code sent to you,
hands you the tab first and continues once you say you&#x27;re done. In clients that support
questions during a task (`tasks.requests.elicitation.create`, as in Claude Code), the question
appears in your conversation; elsewhere the task ends with the question, and you answer by calling
it again with `humanReply`.

`browser_stop_task` stops a running task at the end of its current step.

**Keep your API key out of files that get committed.** If your client can expand environment
variables in its config, use that; otherwise keep the key in a config file outside the repository
and point at it with `--config`.

## Notes

- **Claude Code keeps old tool definitions in a conversation.** After BrowserDo is upgraded, start
  a new conversation to see new tools and parameters.
- BrowserDo speaks MCP protocol version `2025-11-25` and negotiates down to older versions.

## Development```bash
npm install
npm run build
npm test          # 902 tests
npm run test:fast # unit and module tests only

See test/README.md for the test layout.

License

BrowserDo is licensed under the Apache License, Version 2.0; see LICENSE. The Embiody
browser it installs is covered by the Embiody EULA.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
BrowserDo 怎么安装?

在客户端按下面的安装命令接入:npx -y browserdo-mcp。装完在客户端配置里引用同一个包或端点。

BrowserDo 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

BrowserDo 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

BrowserDo 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

BrowserDo 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Cline、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

BrowserDo 能提供哪些能力?

资料显示能力标签包括 网页抓取。具体工具清单以官方文档为准。

BrowserDo 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

BrowserDo 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。