Browser Use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
作者提供的说明(英文原文)
Undetectable browser automation for LLM agents, spoken over MCP.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"zendriver": {
"command": "uvx",
"args": [
"zendriver-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add zendriver -- uvx zendriver-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"zendriver": {
"command": "uvx",
"args": [
"zendriver-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"zendriver": {
"type": "stdio",
"command": "uvx",
"args": [
"zendriver-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 bituq 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.3.4)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Browser Use, Chrome DevTools MCP, MCP Server Browser
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Undetectable browser automation for LLM agents, spoken over MCP.
zendriver-mcp is an MCP server that gives your coding agent (Claude, Cursor, Gemini, Copilot) a real Chrome browser it can actually use on the real web - behind Cloudflare, behind login walls, on pages that detect and block WebDriver.
It's built on Zendriver, which speaks the Chrome DevTools Protocol directly instead of going through WebDriver. That means no navigator.webdriver flag, no headless telltales, and a fingerprint that looks like an ordinary Chrome install.
On top of that foundation, zendriver-mcp layers everything an agent needs to get work done: a token-efficient DOM walker, an accessibility tree with stable uids, performance traces, Lighthouse audits, heap snapshots, human-like input, device emulation, cookie round-tripping, and more - 96 tools across 22 modules.
.heapsnapshot format, Lighthouse audits via the Lighthouse CLI reusing the same browser.prefers-color-scheme.| Module | Tools |
|---|---|
browser | start, stop, status |
navigation | navigate, back, forward, reload, page info |
tabs | new / list / switch / close |
elements | click, type, clear, focus, select, upload |
query | find element(s), text, attributes, buttons, inputs |
content | HTML, text, interaction tree, scroll |
storage | cookies (document.cookie), localStorage |
logging | network + console logs, wait-for-request |
forms | fill form, submit, key press, mouse click |
utils | screenshot, execute JS, wait, security audit |
stealth | Cloudflare bypass, UA / locale / timezone / geolocation overrides |
humanlike | human_click, human_type, estimated_typing_duration |
emulation | viewport, device presets, CPU + network throttle, media |
devtools | start/stop trace, take heap snapshot |
lighthouse | run audit, check CLI availability |
screencast | start / stop (writes frame directory) |
accessibility | AX snapshot with stable uids, click_by_uid, describe_uid |
cookies | export / import / list / clear (CDP-level, all origins) |
network_control | block URLs, extra headers, bypass service worker |
permissions | grant / reset, list names |
proxy | configure / clear (restarts browser with proxy args) |
interception | mock_response, fail_requests, list, stop |
screencast | + export_screencast_mp4, check_ffmpeg_available |
Full signatures live in the docstrings of src/tools/*.py and are auto-listed by the MCP handshake.
Published on PyPI: https://pypi.org/project/zendriver-mcp/.
Requires Python 3.10+ and a Chrome / Chromium install.
# Zero-setup, re-resolves on every run - great for Claude Desktop configs
uvx zendriver-mcp
uv tool install zendriver-mcp pipx install zendriver-mcp pip install zendriver-mcp
{
"mcpServers": { "zendriver": { "command": "uvx", "args": ["zendriver-mcp"] } } }
No clone, no --directory, no absolute path. If you prefer a permanent install instead, swap "command": "uvx" for "command": "zendriver-mcp" after running uv tool install zendriver-mcp.
Working on zendriver-mcp itself? Clone + uv sync, then point your MCP client at the checkout:
{
"mcpServers": { "zendriver": { "command": "uv", "args": ["--directory", "/absolute/path/to/zendriver-mcp", "run", "zendriver-mcp"] } } }
Optional flags on the CLI:
--browser-path /path/to/chrome - point at a specific Chrome binary--transport stdio - only stdio for now; SSE/HTTP arrive when upstream mcp ships stable support# Ask the browser to start, log in once, save the session.
await start_browser() await navigate("https://example.com/login") await fill_form({"#email": "me@me.com", "#pw": "..."}) await export_cookies("~/sessions/example.json")
await start_browser() await import_cookies("~/sessions/example.json") await navigate("https://example.com/dashboard")
snap = await get_accessibility_snapshot() await click_by_uid("ax_1b2c3d4e")
await start_trace() await human_click(selector="#buy-now") await stop_trace("/tmp/buy-flow.json") # loads in Chrome DevTools
await run_lighthouse("https://example.com", form_factor="mobile")
The interaction tree emits compact rows like {"id": 1, "t": "btn", "l": "Search", "r": "hdr"}:
t (type), l (label), r (region)aria-label, aria-labelledby, associated , placeholder, text, title, althdr, nav, main, side, ftr, dlgbutton -> btn, checkbox -> chk, etc.Reported reduction on perplexity.ai: ~96% fewer tokens than raw HTML (~11k -> ~400).
For flows that span multiple actions, prefer get_accessibility_snapshot + click_by_uid - the uids stay valid as long as the underlying backend node survives, even across re-renders.
uv sync
uv run ruff check . uv run ruff format --check . uv run mypy src uv run pytest
CI runs the same four on every push and PR.
Everything on the original roadmap shipped in the 0.2 / 0.3 releases:
Fetch.enable)--proxy-server)ToolResponse envelope adopted in rich-output toolsDocumentation site: [https://bituq.github.io/zendriver-mcp/](https://bituq.github.io/zendriver-mcp/)
What's next is driven by actual usage. Ideas on deck:
mock_responseFetch.enable with patterns (faster than our "match all then filter")MIT. See LICENSE.