nodriver — Chrome browser automation MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        config_path = os.path.join(config_dir, config_file)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add nodriver-mcp-server -- uvx nodriver-mcp

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

[mcp_servers.nodriver-mcp-server]
command = "uvx"
args = ["nodriver-mcp"]

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

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

Optional settings from the registry entry, left out of the block above: 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).