MCP.Market

nodriver — Chrome browser automation MCP server

by andresolbach·io.github.andresolbach/nodriver-mcp-server·v2.6.1·6 stars
No reviews yet

Chrome automation via nodriver: 70 tools, isolated browsers, profiles and configurable startup.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

6 stars123 downloads/wk

Reviews

Write one

Nobody has reviewed nodriver — Chrome browser automation yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

nodriver — Chrome browser automation tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • decorator

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

1 medium
  • Code scan9 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 15 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    nodriver_mcp-2.6.1/src/nodriver_mcp/server.py: … style", "kEvalViolation": "eval()", "kWasmEvalViolation": "W…
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How nodriver — Chrome browser automation compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 65% of 867 Scraping and browsing servers
Tools
1
the typical Scraping and browsing server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
6
more than 75% of 584 Scraping and browsing servers
Downloads a week
123
more than 60% of 312 Scraping and browsing servers with a package

What its tools let an agent do: 1 read

Release history: 4 versions in the registry since 2026-08-25, latest 2026-10-16, typically one every 21 days.

Install nodriver — Chrome browser automation in Claude Code, Cursor or VS Code

claude mcp add nodriver-mcp-server -- uvx nodriver-mcp
Add to Cursor

What the publisher says

From the nodriver — Chrome browser automation repository's README, as published. We do not edit it. Read it on GitHub

nodriver-mcp-server

<!-- mcp-name: io.github.andresolbach/nodriver-mcp-server -->

An undetected, anti-bot-resistant browser automation MCP server — a drop-in, stealth alternative to chrome-devtools-mcp for AI agents like Claude, Claude Code, Cursor, Windsurf, and any Model Context Protocol client. Powered by nodriver so your agent can browse, scrape, and automate real Chrome without tripping Cloudflare, hCaptcha, or WebDriver fingerprint detection.

Keywords: MCP server · browser automation · undetected chromedriver · anti-bot · Cloudflare bypass · web scraping · Claude · Cursor · nodriver · chrome-devtools-mcp alternative · Playwright/Puppeteer alternative · AI agent tools.

Is this the problem you have?

If you drive a browser from an AI agent, you have probably run into one of these:

  • The page sits on "Just a moment…" or "Checking your browser before accessing" and never loads
  • A "Verify you are human" checkbox that reappears every single time you click it
  • "Unusual Activity Detected", "Access Denied", or a plain HTTP 403 — from a site that opens perfectly in your normal browser
  • navigator.webdriver returns true, and the site quietly serves you different content because of it
  • The login works when you do it by hand, and fails the moment automation does the same steps
  • It all worked for weeks, then the site started returning an empty page or a captcha wall

None of that is your script being wrong. It is anti-bot detection — Cloudflare, DataDome, PerimeterX, Akamai, hCaptcha — recognising the automation stack itself. It shows up with chrome-devtools-mcp, playwright-mcp, Puppeteer, Selenium and browser-use alike, because they all drive Chrome in ways that leave a detectable signature: a ChromeDriver binary, WebDriver markers, CDP artifacts.

Why this fixes it

nodriver is the successor of undetected-chromedriver. It speaks the CDP protocol directly — no ChromeDriver binary, no Selenium/WebDriver markers — so navigator.webdriver reads false rather than true, and a session looks like a person using Chrome.

This server exposes that through the same tool surface as chrome-devtools-mcp (65 tools), so your agent keeps a familiar API and simply stops getting blocked. Swapping is a config change, not a rewrite.

What it will not do, so you can judge before installing: it does not solve image or text captchas for you, it cannot defeat every protection on every site, and it will not rescue a scraper that hammers a server. If a site blocks you for what you do rather than what you are, no driver fixes that. cf_verify handles the common Cloudflare checkbox challenge; it is not a captcha-solving service.

Does it actually pass? Here is the evidence

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

nodriver — Chrome browser automation: common questions

Is nodriver — Chrome browser automation MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the nodriver — Chrome browser automation safety report
How do I install nodriver — Chrome browser automation?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does nodriver — Chrome browser automation need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is nodriver — Chrome browser automation maintained?
The last commit was 20 days ago (2026-10-16). The latest release is v2.6.1.
What can I use instead of nodriver — Chrome browser automation?
Servers from other publishers that do the same job: Safari MCP server, Agent360 Browser MCP server and Oya Browser MCP server. Compare all nodriver — Chrome browser automation alternatives.
How does nodriver — Chrome browser automation compare with other Scraping and browsing MCP servers?
safety score 85/100 (higher than 65% of 867 Scraping and browsing servers); tools 1 (the typical Scraping and browsing server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to nodriver — Chrome browser automation

Same job from other publishers: the closest match first, then the best rated.

All nodriver — Chrome browser automation alternatives →
  • Safari
    Native Safari browser automation for AI agents — 98 tools, zero Chrome overhead.
    C
  • Agent360 Browser MCP
    Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.
    A
  • Oya Browser
    Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.
    A
  • Browser Gateway
    AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.
    B
  • Tap
    Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
    B