mcp-chrome-launcher
Related Servers
Alternatives to mcp-chrome-launcher
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.3215,256 npm5,681MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools. Provides browser automation, performance analysis, debugging capabilities, and network request monitoring.2,562,190 npm57,558Apache 2.0
- AlicenseNot gradedqualityCmaintenanceShares one Chrome browser across multiple AI coding sessions via an MCP proxy, adding lifecycle management, tool filtering, and anti-detection while wrapping the upstream chrome-devtools-mcp server.2MIT
Related Servers
- AlicenseBqualityCmaintenanceEnables local AI agents to drive the user's real Chrome session through MCP tools, preserving existing logins and extensions without a debug port or separate profile. Supports tab groups, navigation, page reading, interaction, screenshots, and safe multi-agent sharing over a local bridge.21226 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive the real Chrome browser you already have open, so agents can read logged-in pages, click, fill forms, take screenshots, and inspect tabs, cookies, and network traffic. All communication stays on your machine, with no debugging port or manual cookie copying required.1 npmISC

Dooza Browserofficial
AlicenseNot gradedqualityCmaintenanceGives AI agents a single shared, logged-in Chrome they can drive over MCP or plain HTTP: open and read tabs, click, type, upload files, run short Playwright scripts, hand off whole web tasks to a cheaper model, and keep per-site memory. Agents work in background windows they own without stealing the user's mouse or closing their tabs.MIT- AlicenseNot gradedqualityBmaintenanceA local, open-source Chrome browser-automation MCP server for AI agents that controls real signed-in Chrome profiles with multi-profile routing and parallel tabs.190 npm12MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding assistants drive the user's own already-signed-in Chrome, so agents can read logged-in pages, click, fill forms, navigate, screenshot, inspect network traffic and storage, and run multi-step browser workflows without a separate headless browser or remote debugging port. All communication stays on the user's machine and agent-opened tabs are grouped so they never steal focus.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI assistants drive your real, already-logged-in Chrome through a browser extension, so agents can read, click, type, navigate, screenshot, inspect network traffic, and manage cookies or storage on pages that require existing sessions. It works without opening a remote-debugging port and keeps all communication on your machine.1 npmISC
TDQS
Scored across 33 tools
Most tools target clearly distinct resources or actions (navigation, page lifecycle, console, network, performance, memory). The main overlap is among input tools—type_text, fill, fill_form, and press_key—where an agent could misselect despite the descriptions clarifying intended use cases. Screenshot/snapshot/screencast tools are also somewhat adjacent but distinguishable.
The surface is overwhelmingly snake_case and readable, but conventions vary: most tools use verb_noun (list_pages, navigate_page), several domain tools use noun_verb (performance_start_trace, screencast_start), and some are bare verbs (click, drag, hover, fill). These deviations are minor and predictable within domains, but not fully uniform.
At 33 tools the surface is heavy, though the Chrome automation/DevTools domain is inherently broad. Many tools are specialized and earn their place (performance tracing, heap snapshot, logpoints, lighthouse, CSS inspection), but the overall count is on the high end and may overwhelm routine agent workflows.
Coverage is strong across page lifecycle, navigation, input, forms, dialogs, uploads, screenshots/snapshots, console, network, performance, memory, CSS, emulation, and logpoints. Minor gaps remain around browser storage/cookies, direct DOM/HTML retrieval, and network interception, but most core workflows are supported.