nodriver — Chrome browser automation MCP Server

What this does

nodriver — Chrome browser automation exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

NODRIVER_HEADLESS
NODRIVER_USER_DATA_DIR
NODRIVER_BROWSER_PATH
NODRIVER_PROXY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install nodriver — Chrome browser automation?

Run the Claude Code command in the install section to add nodriver — Chrome browser automation to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with nodriver — Chrome browser automation?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to nodriver — Chrome browser automation as well.

Does nodriver — Chrome browser automation need an API key?

This listing does not flag an API key as required. The server can use these environment variables: NODRIVER_HEADLESS, NODRIVER_USER_DATA_DIR, NODRIVER_BROWSER_PATH, NODRIVER_PROXY; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.