22nd of 6 in MCP servers for developers
chrome-devtools-mcp
MCP server that lets coding agents drive and debug a live Chrome
- Stars
- 53.2k
- License
- Apache-2.0
- Last commit
- Oct 2026
- Last release
- Sep 2026
- Language
- TypeScript
Overview
chrome-devtools-mcp is an MCP server that gives coding agents such as Claude, Cursor and Copilot control of a live Chrome browser. It records performance traces through Chrome DevTools, inspects network requests and console messages with source-mapped stack traces, and automates page actions via puppeteer. A CLI is included for use without MCP, and a --slim mode exposes a smaller tool set.
Who it is for: Developers who want their coding agent to debug and test pages in Chrome
Strengths
- Records DevTools performance traces and extracts insights from them
- Puppeteer-based automation waits for action results automatically
- Slim mode limits the exposed tools to basic browser tasks
- Also ships a CLI for use without an MCP client
Weaknesses
- Usage statistics are sent to Google by default; opt out with --no-usage-statistics
- Performance tools may send trace URLs to the Google CrUX API
- Officially supports only Chrome and Chrome for Testing
- Exposes all browser content to the connected MCP client
What it needs
- no GPU
- Needs Node.js LTS, npm, Google Chrome (current stable)
Also in MCP servers for developers
See all 6| Rank | Project | Score |
|---|---|---|
| 1 | codegraphLocal code knowledge graph served to coding agents over MCP | 80 out of 100 |
| 3 | codebase-memory-mcpMCP server that indexes codebases into a queryable knowledge graph | 62 out of 100 |
| #4 | context7Fetches current, version-specific library docs into coding agent prompts | 57 out of 100 |
| #5 | github-mcp-serverMCP server exposing GitHub repos, issues, PRs and Actions to AI tools | 54 out of 100 |
| #6 | cli-anythingGenerates command-line wrappers so AI agents can drive desktop and backend software | 43 out of 100 |