chrome-devtools-mcp
MCP serverDev toolschrome-devtools-mcp is an MCP server that connects an AI agent to Chrome DevTools. It lets the agent inspect and debug web pages by controlling the browser's developer tools. Use it when you want an agent to look at page structure, network activity, or console output while you work.
Unavailable. This server has no hosted endpoint yet, so Ahel can't serve it.
Add to setup to save this item as a reference. Ahel cannot run it, and signing in will not install it.
What your AI can do with it
- Inspect and debug web pages through Chrome DevTools
- Control Chrome DevTools from an AI agent
- Examine page structure and network activity
- Read console output during debugging
Getting started
- Save this item in Your setup as a reference.
- Read the source or reference documentation for its setup requirements. Saving it here does not connect it to your AI.
- Check this page for availability before trying to install it through Ahel.
From the project's README
As published by chromedevtools/chrome-devtools-mcp in README.md. This repository publishes several servers, so only the opening is shown here.
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot)
control and inspect a live Chrome browser. It acts as a Model-Context-Protocol
(MCP) server, giving your AI coding assistant access to the full power of
Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.
A [CLI][cli] is also provided for use without MCP.
[Tool reference][tool-reference] | [Changelog][changelog] | [Contributing][contributing] | [Troubleshooting][troubleshooting] | [Design Principles][design-principles]
Key features
Shortened here. Read the whole README on GitHub.
Signals
- GitHub stars
- 53k
- Forks
- 5k
- Last commit
- Sep 2026
- Weekly downloads
- 1.7M
What people say
Posts are mostly promotional, but users report liking it for letting coding agents debug web apps in a real browser (console, network, performance traces), with one calling it their favorite MCP server. The only recurring criticism mentioned is high token consumption (18K tokens), and that appears in just one post.
- Praised for
- lets agents debug in a real browser (console, network, perf
- works with Claude Code, Cursor, Gemini CLI
- free and open-source
Summarized from 13 public posts. Opinions are theirs, not Ahel's.
Questions
- What is chrome-devtools-mcp?
- It is an MCP server for Chrome DevTools. It lets an AI agent control Chrome DevTools to inspect and debug web pages.
- What can it do?
- It lets an agent inspect and debug web pages by controlling Chrome DevTools, including looking at page structure, network activity, and console output.
- Do I need Chrome installed?
- Yes, Chrome and Chrome DevTools must be available on your machine for the server to work.
- Is it an MCP server or a plugin?
- It is an MCP server, not a plugin or a browser extension.
Advanced
- Delivery
- chrome-devtools-mcp MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
io-github-chromedevtools-chrome-devtools-mcp- Source
- github.com/chromedevtools/chrome-devtools-mcp
github.com/chromedevtools/chrome-devtools-mcp