Nodriver — undetected browser automation MCP Server

Undetected anti-bot Chrome automation. 70 tools, parallel isolated browsers.

Local serverstdio

What is the Nodriver — undetected browser automation MCP Server?

Nodriver — undetected browser automation is an MCP integration. Undetected anti-bot Chrome automation. 70 tools, parallel isolated browsers.

Packages and local setup

The published pypi package is nodriver-mcp, version 2.5.0. Its declared MCP transport is stdio.

The package declares NODRIVER_HEADLESS: Run Chrome headless (true/false). Default false.; NODRIVER_USER_DATA_DIR: Explicit persistent Chrome profile directory. Default: an ephemeral temp profile, auto-deleted per session.; NODRIVER_BROWSER_PATH: Path to the Chrome/Chromium executable. Auto-detected when unset.; NODRIVER_PROXY: Proxy server address passed to Chrome as --proxy-server..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 2.5.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related browser automation MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
NODRIVER_HEADLESSRun Chrome headless (true/false). Default false.Optional
NODRIVER_USER_DATA_DIRExplicit persistent Chrome profile directory. Default: an ephemeral temp profile, auto-deleted per session.Optional
NODRIVER_BROWSER_PATHPath to the Chrome/Chromium executable. Auto-detected when unset.Optional
NODRIVER_PROXYProxy server address passed to Chrome as --proxy-server.Optional