Chrome DevTools MCP is an MCP server that lets coding agents control and inspect a live Chrome browser for automation, debugging, screenshots, network analysis, console inspection, and performance tracing. It is for developers who want AI coding assistants to test and diagnose web applications, and the catalogue add-ons provide workflows for using those browser tools.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ChromeDevTools/chrome-devtools-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/chromedevtools/chrome-devtools-mcp/gemini-extension)<a href="https://agentmods.dev/plugins/chromedevtools/chrome-devtools-mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/chromedevtools/chrome-devtools-mcp/gemini-extension.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
chrome-devtools-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- chrome-devtools-mcp — 100% identical, 4 lines differ
- chrome-devtools-mcp — 100% identical, 0 lines differ
What it actually says
{
"name": "chrome-devtools-mcp",
"version": "1.8.0",
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"[email protected]"
]
}
}
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 13 lines scan A 2120ea03f5bf
chrome-devtools-mcp is a plugin published in the GitHub repository ChromeDevTools/chrome-devtools-mcp (51,315 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other plugins, from other repositories
brave-devtools-mcp
Reliable automation, in-depth debugging, and performance analysis in Brave using DevTools and Puppeteer.
firefox-devtools-mcp
Control Firefox for browsing, web testing, and debugging. Fill forms, capture network and console activity, take screenshots, run scripts, and profile performance. Supports Android devices.
firefox-devtools-troubleshoot
Diagnose and fix Firefox DevTools MCP setup issues. Use this if the firefox-devtools-mcp plugin is not working.
webview-devtools-mcp
DevTools for any WebView — no remote-debugging port required. Works in Safari/iOS WebView/Lark Web App and more.
pwa-debug
Browser-side debug layer that exposes live PWA state (DOM, framework state, stores, events, library popups) to AI agents via MCP — eliminating the human copy/paste loop when debugging web apps with AI.
webgpu-metal-debug-kit
Debug Chrome WebGPU apps on macOS — browser-level via Chrome DevTools MCP, GPU driver-level via Xcode xctrace Metal System Trace.