browserdo

mcp
Guvenlik Denetimi
Basarisiz
Health Uyari
  • License — License: Apache-2.0
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Basarisiz
  • process.env — Environment variable access in scripts/build-mcpb.mjs
  • process.env — Environment variable access in scripts/dump-snapshot.mjs
  • fs.rmSync — Destructive file system operation in scripts/save-profile-baseline.mjs
  • process.env — Environment variable access in scripts/save-profile-baseline.mjs
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

MCP server for Embiody, the Windows browser your AI agent works in while you keep using your PC.

README.md

BrowserDo

Website: embiody.com/browserdo

Listed on mcpservers.org

BrowserDo demo: the agent fills 4 form fields in 2.5 seconds, shops in its own tabs, keeps going while minimized, fills a checkout in one combo and hands you the tab to pay

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

Tokens per whole-page snapshot: Playwright MCP, Chrome DevTools MCP and BrowserDo on Wikipedia, GitHub, CNN, ESPN and Apple

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
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. A step can wait for
a text to appear and aim at the element showing it ("type, wait for the suggestions, click the
second one" in one call), and the snapshot can be cut to the lines that changed.

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

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:

{
  "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 (all projects) or .cursor/mcp.json (one project):

{
  "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:

{
  "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):

{
  "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:

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

The skill

The browserdo skill tells your agent when and how to use these tools, for example to search
with BrowserDo instead of a built-in search tool. BrowserDo installs it the first time it starts
(see Privacy). To install it on its own, for example before adding BrowserDo, run
npx skills add zhaijunlong/browserdo -g (the skills command needs Node.js 22.20 or newer). An
agent that has the skill but not the tools offers to add BrowserDo for you.

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; changesSince gives only the lines changed since an earlier snapshot.
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 (whole, only the changes, or none). A step can aim by text at what an earlier one made appear, and may be skipped when it fails. Stops at the first failure otherwise.
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 <path>). 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.
  • Skill files: when it starts, BrowserDo puts its skill in ~/.claude/skills/browserdo (read
    by Claude Code), ~/.agents/skills/browserdo (Codex, Cursor, Gemini CLI) and
    ~/.copilot/skills/browserdo (GitHub Copilot in VS Code), each only when such an agent is
    installed. It never replaces a skill of the same
    name that it did not put there, keeps its own up to date, and does not put one back once you
    delete it. The Claude plugin carries the skill itself, so with the plugin it leaves
    ~/.claude/skills alone.
  • 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.

"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'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'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

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.

Yorumlar (0)

Sonuc bulunamadi