Our take
Activeregular commits and releases- Activity
- 86
- Community
- 88
- Issues
- 73
- Pull requests
- 56
+510 stars in the last 8 days
- Releases more often than 87% of the projects we track
- Merges more pull requests than 78% of the projects we track
- More contributors than 77% of the projects we track
This is a focused, actively maintained bridge between coding agents and Chrome DevTools, with a broad contributor base and rapid reported issue and pull request handling.
Good fit if
- Your coding agent supports MCP and needs real Chrome automation, debugging, or performance inspection.
- You want a Node.js-based tool with frequent releases and ongoing commits, and Apache-2.0 licensing suits your project.
- Your team can use Google Chrome or Chrome for Testing and is comfortable configuring an MCP client.
Look elsewhere if
- You need officially supported automation for browsers other than Google Chrome or Chrome for Testing.
- You cannot allow an MCP client to inspect, debug, or modify browser data, or your policy disallows the documented usage statistics collection by default.
- You need browser automation without a Node.js LTS runtime and npm.
All health signals
| Last commit | 2026-10-08 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 48 (latest chrome-devtools-mcp-v1.10.1, 2026-09-23) |
| Contributors | 100+ (top contributor: 31% of commits) |
| Issues closed, last 90 days | 20+ (typically closed in 2 days) |
| Pull requests merged, last 90 days | 56 (typically merged in 1 day) |
| Project age | 13 months |
Checked on 2026-10-09 with the GitHub API.
Overview
Chrome DevTools MCP connects coding agents to a live Chrome browser through the Model Context Protocol, with a CLI available for use without MCP. It addresses the gap between an agent's code changes and what actually happens in a browser by exposing browser automation and DevTools inspection capabilities.
It is aimed at developers using agent clients that need to reproduce browser behavior, diagnose issues, or assess page performance. The project officially supports Google Chrome and Chrome for Testing, and can also run in a slim mode for basic browser tasks.
Key Features
- Automates Chrome using Puppeteer and waits for action results.
- Records performance traces through Chrome DevTools and extracts performance insights.
- Inspects network requests and browser console messages, including source-mapped stack traces.
- Captures screenshots to support debugging and visual inspection.
- Offers an MCP server for coding agents and a CLI for direct use.
- Supports headless and slim modes, along with configuration for persistent profiles and connections to an existing browser.
- Can be used for concurrent sessions and Android debugging, as described in its advanced usage documentation.
Use Cases
- A coding agent can open a page after a code change and investigate console errors or failed network requests, helping frontend developers debug in-browser behavior.
- A developer can ask an agent to record a performance trace and review the resulting insights when assessing a web page's speed.
- Teams building agent products can use the server as a browser subagent foundation rather than implementing Chrome control from scratch.
- Developers who need lightweight browser automation can configure slim, headless mode for basic tasks without the full set of tools.
What you need
Detected in the repository
- Node.js ^20.19.0 || ^22.12.0 || >=23 (from package.json)
- A test suite and automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Add this server to an MCP client configuration:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
See the repository README and its client configuration guide for setup details.
Alternatives
- browser-rs-mcp: It uses Rust and lets multiple agents control separate tabs in a shared Chrome profile, while chrome-devtools-mcp is a TypeScript DevTools MCP server.
- stagehand: It is a browser automation SDK with natural-language actions and data extraction, rather than an MCP server focused on Chrome DevTools inspection and control.
- brightdata-mcp: It provides remote browser automation alongside web search and scraping through Bright Data infrastructure, rather than controlling a local live Chrome browser.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| chrome-devtools-mcp | TypeScript | Apache-2.0 | 53.1k | Active |
| browser-rs-mcp | Rust | Apache-2.0 | 25 | New |
| stagehand | TypeScript | MIT | 25.5k | Active |
| brightdata-mcp | JavaScript | MIT | 2.7k | Active |
Considerations
The project is active rather than a long-established, slow-changing dependency: repository data reports regular commits and releases, with a latest release in September 2026. It has at least 100 contributors and the measured top contributor share is about 31%, so work is not concentrated in a single person. Reported median times to close issues and merge pull requests are short, though those metrics do not guarantee a particular support outcome.
The server exposes browser contents to connected MCP clients, which may inspect, debug, and modify browser data. Usage statistics are enabled by default, and performance tooling may send trace URLs to the Google CrUX API; the README documents flags and environment variables for opting out. The README also limits official support to Google Chrome and Chrome for Testing, so other Chromium-based browsers may behave unexpectedly.
Found this useful?
Share it with someone who would like chrome-devtools-mcp.