
Zendriver MCP
io.github.bituqPublished by GitHub account bituqv0.3.4Updated Nov 3, 2026
Undetectable browser automation for LLM agents, spoken over MCP.
Overview
Local MCP server that gives an AI agent a real Chrome browser to drive the web, with stealth, DevTools, Lighthouse and cookie-session tools.
- What you can do
- Start, stop and check a Chrome browser, then navigate, go back/forward, reload and manage tabs
- Find and interact with page elements: click, type, clear, focus, select, upload, fill and submit forms
- Read page content: HTML, text, token-efficient interaction tree, accessibility snapshot with stable uids, screenshots, execute JS
- Inspect network and console logs, block URLs, add headers, mock or fail requests, grant permissions, set a proxy
- Manage sessions: export/import cookies and localStorage, override user agent, locale, timezone and geolocation, emulate devices and network conditions
- Profile and record: performance traces, heap snapshots, Lighthouse audits, screencasts to JPEG/PNG or MP4
- When to use it
- Useful when an agent needs to operate a real browser on live sites: logging into a site once and reusing the session, walking through multi-step flows, or auditing pages for performance and accessibility. Also suited to sites that block WebDriver-based automation.
- Requirements
- Runs locally over stdio as a PyPI package (zendriver-mcp), launched for example with uvx or installed via uv tool, pipx or pip. Needs Python 3.10+ and a Chrome or Chromium installation; an optional flag can point at a specific Chrome binary. Lighthouse and MP4 screencast export depend on external CLI tools being available.
Installation
In SourceWeft
- Open Zendriver MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
zendriver-mcp
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.
Highlights
- Undetectable by design. Zendriver keeps a clean fingerprint; we ship a Cloudflare Turnstile solver, identity overrides (UA, locale, timezone, geolocation), and bezier-curve mouse movement plus gaussian typing timing.
- Token-efficient DOM. Two ways to see the page - the upstream DOM walker that reports 96% fewer tokens than raw HTML, and a CDP accessibility tree keyed by stable uids that survive re-renders.
- Full DevTools parity. Performance traces that load in Chrome DevTools,
heap snapshots in the standard
.heapsnapshotformat, Lighthouse audits via the Lighthouse CLI reusing the same browser. - Session round-tripping. Export all cookies (including HTTP-only ones) to JSON, re-import on the next session. Log in once, reuse everywhere.
- Emulation. iPhone 15 Pro, Pixel 8, iPad Pro, and desktop presets; CPU
throttling; Slow 3G / Fast 3G / 4G / offline network profiles; force
prefers-color-scheme. - Screencasts. Write frames to disk as JPEG or PNG at configurable FPS.
Tool catalogue
Full signatures live in the docstrings of src/tools/*.py and are auto-listed
by the MCP handshake.
Install
Published on PyPI: https://pypi.org/project/zendriver-mcp/.
Requires Python 3.10+ and a Chrome / Chromium install.
Use with Claude Desktop / Claude Code
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.
Development checkout
Working on zendriver-mcp itself? Clone + uv sync, then point your MCP
client at the checkout:
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 upstreammcpships stable support
The 30-second tour
Token-optimised DOM walker
The interaction tree emits compact rows like
{"id": 1, "t": "btn", "l": "Search", "r": "hdr"}:
- Compact keys:
t(type),l(label),r(region) - Smart labels: inferred from
aria-label,aria-labelledby, associated<label>,placeholder, text,title,alt - Noise filtering: SVG internals, nested interactive children skipped
- Region tagging:
hdr,nav,main,side,ftr,dlg - Type compression:
button->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.
Development
CI runs the same four on every push and PR.
Roadmap
Everything on the original roadmap shipped in the 0.2 / 0.3 releases:
- Stealth: Cloudflare solver, UA / locale / timezone / geolocation
- Human-like input: bezier mouse paths, gaussian keystroke timing
- DevTools parity: traces, heap snapshots, Lighthouse
- Screencast + mp4 export via ffmpeg
- Accessibility tree with stable uids
- Cookie import/export, blocking, extra headers, permissions
- Request interception + response mocking (
Fetch.enable) - Proxy configuration (restart with
--proxy-server) -
ToolResponseenvelope adopted in rich-output tools - PyPI publish workflow (Trusted Publishing)
Documentation site: https://bituq.github.io/zendriver-mcp/
What's next is driven by actual usage. Ideas on deck:
- Per-request proxy routing via Fetch interception
- Binary body support in
mock_response Fetch.enablewith patterns (faster than our "match all then filter")
License
MIT. See LICENSE.
Acknowledgements
- Zendriver does the heavy lifting underneath.
- The token-optimised DOM walker and the original 49-tool foundation come from ShubhamChoulkar/Zendriver-MCP. This project started as a fork and has since grown its own identity and feature set.
Source: README.md at commit f360eb2
Tools
0Version history
1- v0.3.4LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts