ChromeDevTools/chrome-devtools-mcp

Chrome DevTools for coding agents

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 33 minutes ago
Added to GitGenius on December 14th, 2025
Created on September 11th, 2025
Open Issues & Pull Requests: 217 (+0)
GitHub issues: Enabled
Number of forks: 5,827
Total Stargazers: 53,129 (+6)
Total Subscribers: 256 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.5 hours
Mean response time: 4.3 days
90th percentile: 6.0 days
Tracked items: 562

How this project is maintained

About 17% of issues opened in the past year have never received a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "p2" is answered fastest, typically in about 2 hours, while "documentation" waits about 2 days. 18% of tracked open issues have had no activity in three months. 70% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 177
New in 7 days: 113
Closed in 7 days: 12
Avg open age: 68 days
Stale 30+ days: 57
Stale 90+ days: 28

Recent activity

Opened in 7 days: 113
Closed in 7 days: 12
Comments in 7 days: 20
Events in 7 days: 138

Top labels

  • confirmed (162)
  • collecting-feedback (93)
  • feature (83)
  • p3 (31)
  • documentation (15)
  • p2 (12)
  • p1 (8)
  • client-claude (7)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Chrome DevTools for agents is an MCP server that lets coding agents control and inspect a live Chrome browser through the Model-Context-Protocol.

The tool solves the problem of giving AI coding assistants reliable access to browser automation and debugging capabilities. It works by exposing Chrome DevTools functionality through an MCP server interface, allowing agents to record performance traces, analyze network requests, take screenshots, inspect console messages with source-mapped stack traces, and automate browser actions using Puppeteer. The tool automatically waits for action results to ensure reliable automation.

Developers should adopt this tool if they are building AI coding agents that need to interact with web applications or perform browser-based testing and debugging. It suits projects where an agent needs to gather performance insights, debug web applications, or automate browser workflows. The tool officially supports Google Chrome and Chrome for Testing; other Chromium-based browsers may work but are not guaranteed. A CLI is also provided for use cases that do not involve MCP.

The project maintains a substantial base of adopters, as evidenced by the fact that almost all open issues are raised by outside users rather than the core team. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by confirmed issues, feedback collection, and feature requests.