What it does
The server exposes 70 tools for controlling Chrome through nodriver. It can run isolated browser instances and work with browser profiles, and its startup behaviour can be configured.
It suits workflows that need Chrome driven programmatically from an MCP-compatible client. The available description is brief, so setup steps and further details are not listed here.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 15 Nov 2026 · its page on the source
nodriver — Chrome browser automation
Chrome automation via nodriver: 70 tools, isolated browsers, profiles and configurable startup.
v2.6.2As shown on registry.modelcontextprotocol.io when we last read it