Home › Browser Automation & Scraping › nodriver — Chrome browser automation

nodriver — Chrome browser automation

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

Python Local macOSWindowsLinux

★ 8 stars Last pushed 2026-10-16 License: MIT

View repository → Website →

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

uvx nodriver-mcp

Or add to your MCP client config:

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

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.