chrome-devtools-mcp

chrome-devtools-mcp is a plugin for Gemini CLI from ChromeDevTools/chrome-devtools-mcp. Its token cost is not measured, scanned A, original, Apache-2.0.

A configuration that connects the agent to Chrome DevTools through an MCP server. Chrome DevTools is the browser's built-in set of tools for inspecting and debugging web pages.

In plain words
What is it for?
It is for setting up Chrome DevTools access for browser inspection and web debugging.
Why use it?
It provides the connection settings needed to use that browser development service instead of configuring it by hand.

Plugin for Gemini CLI

Written for Gemini CLI: a Gemini CLI extension manifest.

Good fit It is for setting up Chrome DevTools access for browser inspection and web debugging.

Compare 6 plugins from other repositories ↓
Install with agentmods
npx agentmods add plugins/chromedevtools/chrome-devtools-mcp/gemini-extension
About the project

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.

ChromeDevTools/chrome-devtools-mcp · 54,101 stars · on GitHub · developer.chrome.com

Install

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.

Clone the repo
git clone --depth 1 https://github.com/ChromeDevTools/chrome-devtools-mcp

Made for: Gemini CLI.

Wrote 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.

agentmods badge for chrome-devtools-mcp

README.md
[![agentmods](https://agentmods.dev/badge/plugins/chromedevtools/chrome-devtools-mcp/gemini-extension/github.svg)](https://agentmods.dev/plugins/chromedevtools/chrome-devtools-mcp/gemini-extension)
Your own site
<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for chrome-devtools-mcp

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

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 2d ago.

The scan reads gemini-extension.json. This mod also ships 59 executable files (scripts/append-lighthouse-notices.ts, scripts/clean-submodules.ts, scripts/count_tokens.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

gemini-extension.json · 13 lines

What it actually says

{
  "name": "chrome-devtools-mcp",
  "version": "1.12.0",
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "[email protected]"
      ]
    }
  }
}
Files

What ships with it

60 files beside gemini-extension.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2d ago Changed 1294498a3997
  2. 9d ago Changed c3bf6e8d1f51
  3. 1mo ago Changed c39b05ef9d4a
  4. 1mo ago Changed e53b8a00ca56
  5. 1mo ago First seen · 13 lines scan A 2120ea03f5bf

Subscribe to this mod's changes

chrome-devtools-mcp is a plugin published in the GitHub repository ChromeDevTools/chrome-devtools-mcp (54,101 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.