Chrome DevTools MCP (benjaminr)
A Python Chrome MCP: the agent connects to Chrome over the DevTools Protocol, reads network, console and cookies, runs JavaScript and takes page metrics
- 312 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent reads and clears browser cookies and storage and runs arbitrary JavaScript on the page
- Chrome starts with a remote debugging port open on your computer
Install
- Works in
Manual install
claude mcp add chrome-devtools "$(pwd)/.venv/bin/python" "$(pwd)/server.py" -e CHROME_DEBUG_PORT=9222Run from the cloned directory after uv sync. The paths must be absolute.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent reads and clears browser cookies and storage and runs arbitrary JavaScript on the page
- Chrome starts with a remote debugging port open on your computer
This is third-party code. Review the repository files before installing.
What it does
A Python server gives Claude Chrome's debugging abilities through the Chrome DevTools Protocol. The agent connects to a web app open in Chrome and works through it during the conversation. Chrome can be launched by the server itself with remote debugging enabled. The tools come in groups. Browser control: start_chrome, start_chrome_and_connect, connect_to_browser and navigate_to_url. Network: a request list filtered by domain and status, and response bodies. Console: logs, an error summary, JavaScript execution, object inspection and live monitoring. Page analysis: metrics, performance data, running code in all frames. Storage: quotas, cookies, clearing by origin. The sources also hold separate CSS and DOM modules. Claude Desktop has a built .dxt extension that installs in one click. Everyone else can start server.py by hand with the CHROME_DEBUG_PORT variable, port 9222 in the examples.
Who it is for. For web developers who want to work through console errors and network requests of their app together with Claude Desktop or Claude Code.
Good fit when
- You want a Python Chrome MCP so the agent can see requests and responses of a local app
- Console errors need to be summarised to find why a page broke
- You need to look inside an object in the browser, for example window, via inspection
- You need page load and resource metrics without opening the DevTools panel
- For Claude Desktop you want a one-click extension install with no config editing
Not a fit when
- You want to drive your everyday browser with tabs and logins: the server launches a separate Chrome with a debugging port
- You need a project with recent updates: the repository's last change is from October 2025
- You need official support from the Chrome DevTools team: a separate server exists for that
- The page holds sensitive data: the tools read cookies and storage and run code on the page
Example request
Start Chrome on localhost:3000, give me an error summary from the console and show network requests with status 500.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
CHROME_DEBUG_PORT- Chrome remote debugging port, 9222 in the examples.
Limitations
Installing in Claude Code needs absolute paths to the Python interpreter and server.py, and relative paths cause start errors. Claude Desktop and Claude Code are supported; for other clients the project gives python server.py. The Chrome path can be set with the chrome_path parameter. The tools read and clear cookies and storage and run arbitrary JavaScript. The license is MIT. Use from Russia was not checked: the server is local and needs no outside keys.
How to disable. Remove the extension in Claude Desktop or run claude mcp remove chrome-devtools. Close the debugging Chrome like any other window.
FAQ
How do I install Chrome DevTools MCP in Claude Code?
Clone the repository, run uv sync and add the server with claude mcp add chrome-devtools using absolute paths to the Python from .venv and to server.py, plus -e CHROME_DEBUG_PORT=9222.
How do I get this Chrome MCP into Claude Desktop in one click?
Download the .dxt file from the repository's Releases, open the extensions section in Claude Desktop and install it. Set the Chrome path in the extension settings if needed.
What data does this server read from Chrome?
Network requests and response bodies, console logs, page metrics, cookies, localStorage and sessionStorage. It also runs JavaScript in the page context.
How does it differ from the official Chrome DevTools MCP?
This server is written in Python by a separate author and works through the Chrome DevTools Protocol. The catalog also has the official server from the Chrome DevTools team with its own set of tools.
What if the server will not start in Claude Code?
Check that the paths are absolute, that the interpreter comes from .venv and that claude mcp get chrome-devtools shows the right command and arguments.
Discussion
No questions or reviews yet.
Related
MCP serversThe Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A Claude Code plugin that drives your Chrome over the DevTools Protocol: tabs, forms, page extraction and screenshots with no third-party dependencies
A skill for Amp, Claude Code and Cursor: the agent drives your live Chrome with its open tabs and signed-in accounts through a single debugging toggle
A Chrome extension with an MCP server: the agent drives your everyday browser with its sessions, tabs, bookmarks and history
DrissionPage MCP: browser control
DrissionPage MCP Server
A Python MCP server for Codex, Claude Code and Cursor: 69 atomic tools for driving Chromium on top of DrissionPage, with page and network observation
An MCP server and Chrome extension that let the agent drive your already open browser with your logged-in sessions, all locally
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Chrome DevTools MCP (benjaminr) (this entry) | no | not required | 312 | |
| Chrome DevTools MCP | yes | not required | 54,001 | the official Chrome DevTools team server, while this is an independent Python implementation |
| Chrome MCP Server | no | not required | 12,502 | a Chrome extension with a server inside, while this launches a separate Chrome with a debugging port |
| chrome-cdp | no | 3,284 | a skill for driving a live Chrome rather than an MCP server |
README in short
The description explains that the server runs inside Claude Desktop and needs no separate processes. It gives four install routes: the prebuilt .dxt extension, the mcp install command, a Claude Code setup and manual config editing. Then come a quick start with the start_chrome_and_connect command, the tool list by group and a walk through typical path problems.