Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Zendriver MCP

by bituqversion 0.3.4i★ –iRuns on your computer
Registry nameio.github.bituq/zendriver-mcp

Install

Overview

Description from the maker (original English)

Undetectable browser automation for LLM agents, spoken over MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "zendriver": {
      "command": "uvx",
      "args": [
        "zendriver-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add zendriver -- uvx zendriver-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "zendriver": {
      "command": "uvx",
      "args": [
        "zendriver-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "zendriver": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "zendriver-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account bituq, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

  • More stars than 0% of the other 1377 servers in this category
  • Published to the registry more recently than 19% of the other 1377 servers in this category
  • Basic checks equal to or better than 100% of the other 1377 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Zendriver MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.4) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 18 days ago
Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 16 days ago
Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 .heapsnapshot format, 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

ModuleTools
browserstart, stop, status
navigationnavigate, back, forward, reload, page info
tabsnew / list / switch / close
elementsclick, type, clear, focus, select, upload
queryfind element(s), text, attributes, buttons, inputs
contentHTML, text, interaction tree, scroll
storagecookies (document.cookie), localStorage
loggingnetwork + console logs, wait-for-request
formsfill form, submit, key press, mouse click
utilsscreenshot, execute JS, wait, security audit
stealthCloudflare bypass, UA / locale / timezone / geolocation overrides
humanlikehuman_click, human_type, estimated_typing_duration
emulationviewport, device presets, CPU + network throttle, media
devtoolsstart/stop trace, take heap snapshot
lighthouserun audit, check CLI availability
screencaststart / stop (writes frame directory)
accessibilityAX snapshot with stable uids, click_by_uid, describe_uid
cookiesexport / import / list / clear (CDP-level, all origins)
network_controlblock URLs, extra headers, bypass service worker
permissionsgrant / reset, list names
proxyconfigure / clear (restarts browser with proxy args)
interceptionmock_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.

Install

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

Or install once, invoke many

uv tool install zendriver-mcp pipx install zendriver-mcp pip install zendriver-mcp

Use with Claude Desktop / Claude Code

{

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

Development checkout

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

The 30-second tour

# 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")

Next run: skip the login entirely.

await start_browser() await import_cookies("~/sessions/example.json") await navigate("https://example.com/dashboard")

Get an accessibility snapshot, click by stable uid.

snap = await get_accessibility_snapshot() await click_by_uid("ax_1b2c3d4e")

Record a performance trace while you click around.

await start_trace() await human_click(selector="#buy-now") await stop_trace("/tmp/buy-flow.json") # loads in Chrome DevTools

Run Lighthouse against the current browser.

await run_lighthouse("https://example.com", form_factor="mobile")

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

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.

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)
  • ToolResponse envelope adopted in rich-output tools
  • PyPI publish workflow (Trusted Publishing)

Documentation site: [https://bituq.github.io/zendriver-mcp/](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.enable with 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.
Ask PopNx