Chrome Devtools Mcp

Features

Headless Browsers - Operates a full-featured web browser without a graphical user interface for high-speed testing and data extraction.
Browser Automation - Runs reliable end-to-end tests by controlling browser instances to verify application behavior.
Web Automation Frameworks - Enables building scripts that navigate websites, click buttons, and extract data without manual human input.
Agentic Browser Controllers - Provides a programmatic bridge that allows autonomous software agents to navigate web pages and interact with elements.
Browser Debugging Protocols - Communicates with the browser engine through a bidirectional JSON-RPC channel to inspect, debug, and manipulate web page states.
Web Interaction Agents - Directs browser instances through an interface to perform repetitive web actions and inspect page elements programmatically.
Model Context Protocol - MCP server for debugging and controlling Chrome.
Model Context Servers - Exposes browser debugging and inspection tools to AI agents.
Browser Automation - Official integration for driving Chrome DevTools and auditing pages.
Command Line Utilities - Official service for browser developer tools integration.
Browser Automation Protocols - Provides a standardized communication interface for controlling web browser instances to perform automated tasks.
Browser Automation Toolkits - Performs web actions like navigation and snapshot capturing by invoking standardized tools through a secure protocol.
Remote Browser Controllers - Uses a standardized messaging interface to send commands and receive events between a client and a remote browser instance.
Browser Session Managers - Launches independent browser processes with unique data directories to ensure secure and isolated automated tasks.
Remote Debugging Tools - Connects development tools to live browser sessions to inspect page structures and troubleshoot issues.
Asynchronous Execution Engines - Processes browser instructions through a non-blocking message queue to enable complex, multi-step web interactions.
Remote Debugging Interfaces - Connects external applications to browser sessions to monitor, manipulate, and troubleshoot live web environments.
Session Orchestration Tools - Organizes active browser sessions by connecting to running instances and handling concurrent users.

Open-source alternatives to Chrome Devtools Mcp

Similar open-source projects, ranked by how many features they share with Chrome Devtools Mcp.

remorses/playwriter
remorses/playwriter
2,866View on GitHub
Playwriter is a browser automation framework and remote controller that manages stateful sessions and executes programmatic commands via the Chrome DevTools Protocol. It provides a system for controlling web browsers to interact with pages and extract data through both programmatic APIs and a command-line interface. The project features a visual element selector that generates screenshots with accessibility labels, mapping visual interface elements to programmatic selectors to help agents navigate. It supports remote browser control through WebSocket tunneling, allowing users to manage browse
HTMLmcpplaywright
View on GitHub2,866
kiwibrowser/src
kiwibrowser/src
2,948View on GitHub
This project is a Chromium-based mobile browser and rendering engine designed for mobile platforms. It functions as a web extension host, allowing the execution of browser extensions within a mobile environment to provide custom functionality. The project distinguishes itself through custom user interface modifications, such as the implementation of a specialized night mode and the relocation of the address bar for improved ergonomics. It also includes a remote debugging interface and protocol that allow an external developer console to connect to a live browser instance for inspecting and tr
View on GitHub2,948
browserless/browserless
browserless/browserless
13,369View on GitHub
Browserless is a service-oriented platform designed for remote browser automation and headless execution. It provides a distributed infrastructure that manages browser sessions through containerized isolation, allowing users to execute scripts and interact with web content without maintaining local browser state or infrastructure. The platform functions as a remote API and WebSocket-based control layer, enabling stateless HTTP requests for tasks like document generation and real-time browser interaction. It incorporates proxy-based routing to manage traffic signatures and supports the integra
TypeScriptbrowserlesschromedocker
View on GitHub13,369
executeautomation/mcp-playwright
executeautomation/mcp-playwright
5,237View on GitHub
This project is a Model Context Protocol server that enables Large Language Models to control Playwright browsers for web automation, scraping, and end-to-end testing. It functions as a programmable interface for executing JavaScript, capturing screenshots, and interacting with web elements across multiple browser engines. The server exposes browser automation capabilities as a set of standardized tools that models can discover and invoke. It supports session-based browser isolation to ensure unique contexts for each client connection and provides a transport layer using either standard input
TypeScript
View on GitHub5,237

See all 30 alternatives to Chrome Devtools Mcp

ChromeDevToolschrome-devtools-mcp

Features

Open-source alternatives to Chrome Devtools Mcp

remorses/playwriter

kiwibrowser/src

browserless/browserless

executeautomation/mcp-playwright

Star history

Open-source alternatives to Chrome Devtools Mcp

remorses/playwriter

kiwibrowser/src

browserless/browserless

executeautomation/mcp-playwright