Open-source browser MCP server · Apache-2.0 · Windows · v0.9 preview

BrowserDo The MCP server for the browser that keeps working in the background

Add BrowserDo to Claude Code, Codex, Cursor or any MCP client, and your agent can work in Embiody, a Windows browser built for agents: at full speed in the background, through sites that block bots, with the sign-ins you already have. You keep using your PC and can step in anytime.

Install BrowserDo View on GitHub

Claude Code: one command. BrowserDo installs the browser on first run.

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

Works with Claude Code, Claude Desktop, Codex, Cursor, VS Code Copilot, Gemini CLI, WorkBuddy, Doubao Work, QwenWork, TRAE and other MCP clients.

See it work

Claude Code compares prices across six stores, reads Reddit, fills in the checkout, then hands you the tab to pay.

Plays from YouTube. Watch on YouTube

How BrowserDo compares

Tested on real sites in October and November 2026. The clip or chart for each row is in Why BrowserDo below.

Test	Other tool	BrowserDo
Walmart, Target, adidas and realtor.com	Playwright MCP: stopped by a bot check	Goes straight through
A privacy overlay on nytimes.com	Playwright MCP: the click lands on the overlay	Sees only the overlay’s buttons and closes it first
The location prompt on McDonald’s store finder	Playwright MCP: the agent never sees it	Reported to the agent, which allows it once
A JB Hi-Fi search page	Claude Code’s WebFetch: 0 products	All 18 products, with prices
Tokens for a whole page on Wikipedia, GitHub, CNN, ESPN and Apple	Playwright MCP, Chrome DevTools MCP: more than twice as many	Less than half (37% of Playwright MCP’s)
A countdown with the window covered for 7 minutes	Regular Chrome: 355 s behind	On time (≤ 1 s)

Why BrowserDo

BrowserDo drives Embiody, a browser built for agents that work while you do something else. The clips and numbers below were recorded on real sites; the side-by-side clips run the same task at the same moment through Playwright MCP and BrowserDo, from one Claude Code session.

Full speed in the background. Your screen stays yours.

Pages keep running at full speed in background tabs, in windows hidden behind other windows, and in minimized or hidden windows. The agent's clicks and typing never pull the browser in front of you.

So your agent can work on a dozen tabs at once while you keep using your computer.

Tabs the agent opens from its own tabs stay with the agent.
Hide the browser to the system tray with one button; the agent keeps working.

Measured

Browser window fully covered by another window for 7 minutes, with a countdown running on the page.

≤ 1 s

Embiody: countdown behind, in front and background tabs

355 s

Regular Chrome: countdown behind (slowed down after 12 s)

Embiody 0.9 vs Chrome 156, Windows, October 2026.

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

Your agent works in your own browser, on your behalf, so sites with anti-bot protection treat it the way they treat you.

And because it is your browser on your PC, your agent works with the sign-ins you already have.

Tested

Same task, same moment: Walmart, Target, adidas and realtor.com stop Playwright MCP with a bot check. Embiody goes straight through.

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.

Sees the whole page. Clicks the right thing.

With other tools, an ad or pop-up covering the page leads to wrong or failed clicks. Embiody filters at the engine level, so your agent only sees what it can actually click.

Reads and clicks inside embedded frames from other sites, such as payment and sign-in forms.
Reads long pages in full.
Scrolls an element into view before clicking it.
Stays accurate across multiple monitors, display scaling and page zoom.
Rejects out-of-date element references instead of clicking the wrong thing.

You can always see what the agent is doing.

Tabs under agent control show a virtual cursor, a highlighted page border and a badge on the tab. Open one and watch the agent work.

Work side by side in the same tabs.

Your agent fills in the forms; you step in for the sign-in, the captcha, the payment or the file to upload, then hand the tab back. No copying links between windows, no starting over: the agent picks up exactly where you left off. Touch a tab the agent is using and Embiody asks whether you want to take over; before the agent touches one of your tabs, it asks first.

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. A whole page takes less than half the tokens of Playwright MCP or Chrome DevTools MCP, and the agent can read just the screen it is working on. Measured on Wikipedia, GitHub, CNN, ESPN and Apple, November 2026.

Combos: many steps, one call

Click, type and press keys in a single call, and get the updated page straight back. Fewer round trips: your agent works faster and uses fewer tokens.

Reads the page's own text

Not a summary: the page itself, including pages built by scripts and sites you are signed in to. A drop-in replacement for Claude Code's built-in WebFetch. A 231,000-character documentation page reads in full in under 2 seconds.

Sees the browser's own pop-ups

Permission prompts, menus, Save As, “Leave site?”, alerts and dialogs are all reported to the agent, together with how each one can be handled.

Current engine, properly shipped

Built on Chromium 156. Digitally signed installers. Automatic updates with signature verification.

BrowserDo MCP tools

Your agent picks the tools itself; you just say what you want done.

`browser_take_snapshot`	The page as one line per element, with a number on every element the agent can act on, plus any popups in the way. Can add an annotated screenshot or read beyond the screen.
`browser_read_pages`	Reads up to 10 pages at once in background tabs and returns their text, links included.
`browser_batch`	Several clicks, typing and key presses on one tab in one call, then a fresh snapshot.
`browser_click`, `browser_input_text`, `browser_press_key`, `browser_select_editable_text`, `browser_scroll`	Act on an element by its number.
`browser_move`, `browser_drag`	Hover, and drag sliders, canvases and reorderable lists.
`browser_navigate`, `browser_go_back`, `browser_go_forward`, `browser_reload`, `browser_stop_loading`, `browser_wait`	Getting around.
`browser_new_tab`, `browser_select_tab`, `browser_close_tab`, `browser_set_audio_muted`	Tabs.
`browser_get_window_info`, `browser_new_window`, `browser_close_window`, `browser_show`, `browser_minimize`	Browser windows.
`browser_close_popup_bubble`	Answers a permission prompt or dialog.
`browser_start_human_control`, `browser_stop_human_control`	Hands the tab to you for a password or captcha, then takes it back.
`browser_status`	Whether the browser is ready, or how far its first install has got.
`browser_run_task`, `browser_stop_task`	Optional: hands a whole task to a vision model at an endpoint you set up, with your own API key, and keeps the screenshots out of your agent’s context.

Settings and the full reference are in the README on GitHub.

Install

Just tell your agent: “Find BrowserDo MCP and install it.” Most agents can do it themselves. BrowserDo is our open-source MCP server (Apache-2.0): through it your agent works in Embiody, which runs on Windows 10 and 11.

Add BrowserDo

Ask your agent as above, or add it yourself with one of the snippets below. Adding it yourself needs Node.js 20 or newer (if you don't have it: winget install OpenJS.NodeJS.LTS, then restart your agent program).

Get the browser

BrowserDo downloads and installs Embiody the first time it runs. Or download the installer yourself.

Ask your agent

“Use BrowserDo to search for BrowserDo Embiody and give me the three most recent results.” If results come back, BrowserDo is installed and working.

Claude Code

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

Claude Desktop

Settings → Developer → Edit Config, add to claude_desktop_config.json, then restart Claude.

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

Codex

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

Or add to ~/.codex/config.toml:

[mcp_servers.browserdo]
command = "npx"
args = ["-y", "browserdo-mcp"]

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

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

VS Code (GitHub Copilot)

Add to .vscode/mcp.json, then use Copilot in agent mode:

{
  "servers": {
    "browserdo": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "browserdo-mcp"]
    }
  }
}

Gemini CLI

Add to ~/.gemini/settings.json:

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

WorkBuddy

In WorkBuddy: 「专家·技能·连接器」→「连接器」→「自定义连接器」→「添加 MCP」. Paste this and save. WorkBuddy brings its own Node.js. If the first connection shows a yellow dot, click refresh.

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

Doubao Work

In Doubao Work: 「插件·技能·工作台」→「添加」→「新建自定义连接器」. Set the transport type to STDIO, the command to npx, and add two arguments, one per row: -y and browserdo-mcp. Doubao Work brings its own Node.js.

npx -y browserdo-mcp

QwenWork

In QwenWork: Skills & extensions → Connectors → Add → Paste JSON Config. Paste this, then Import.

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

TRAE

In TRAE: Settings → MCP → Add → Create Manually (Settings is in the avatar menu). Paste this, then Confirm.

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

Other MCP clients

Add a local (stdio) MCP server with command npx and arguments -y browserdo-mcp.

npx -y browserdo-mcp

FAQ

What is the difference between BrowserDo and Embiody?

Embiody is the browser. BrowserDo is the MCP server that connects your agent to it. You install BrowserDo; it sets up the browser for you.

Is BrowserDo free?

Yes. BrowserDo is open source under Apache-2.0, and the Embiody browser is free to use, including commercially, under our license agreement. We may offer paid editions in the future; they would come with their own terms.

Does the agent use my accounts?

It works in your own Embiody, in its Default profile, so it can use the sites you are signed in to there. It never uses other Embiody profiles or other browsers such as Chrome or Edge. To keep the agent apart, give it a profile folder of its own with EMBIODY_USER_DATA_DIR (see the README).

What happens the first time it runs?

BrowserDo downloads and installs Embiody, about 140 MB, which takes a few minutes. Your agent can call the tools at once; until the browser is ready they reply with the progress. If your agent program says “Failed to connect”, check that Node.js 20 or newer is installed (node -v).

Which agents does it work with?

Any agent that supports MCP, including Claude Code, Claude Desktop, Codex, Cursor, VS Code Copilot, Gemini CLI, WorkBuddy, Doubao Work, QwenWork and TRAE.

Does it work on Mac or Linux?

Not for now. Embiody runs on Windows 10 and 11; whether Mac and Linux come next depends on demand. If you need one, tell us on r/Embiody or GitHub Discussions.

Where does page content go?

Only to the agent program that asked for it, on your computer. If you set up browser_run_task, it also sends screenshots to the model endpoint you configured. BrowserDo has no telemetry. See the Privacy Policy.

Can other programs on my PC control the browser?

Yes, and you should know this. Embiody is made to be driven by agents, so while it runs it accepts control connections from programs on the same computer (never from the network). Only run programs you trust. This is the same as other software that lets programs control a browser. If you have specific security needs, tell us on r/Embiody or GitHub Discussions.

What does “preview” mean?

Version 0.9 works, but it is early. Expect rough edges and frequent updates. Bug reports and ideas are very welcome on r/Embiody or GitHub Discussions.