What is chrome-devtools-mcp?

A plugin configuration that connects an agent to Chrome DevTools and Puppeteer, tools for controlling and inspecting the Chrome browser.

Use it for Chrome browser automation, debugging, and performance analysis.

It gives the agent a defined way to automate browser tasks and inspect debugging and performance information.

chrome-devtools-mcp — Plugin by adilkalam

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.

Claude Code

/plugin marketplace add adilkalam/orca

agentmods

npx agentmods add plugins/adilkalam/orca/chrome-devtools-mcp

Clone the repo

git clone --depth 1 https://github.com/adilkalam/orca

Made for: Claude Code.

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. Scan, not verified.

Origin 89% copy Near-identical to another mod 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 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.

Origin

This is a copy

89% identical to chrome-devtools-mcp — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

mcp/chrome-devtools-mcp/.claude-plugin/plugin.json · 12 lines

What it actually says

{
  "name": "chrome-devtools-mcp",
  "version": "latest",
  "description": "Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer",
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["chrome-devtools-mcp@latest"]
    }
  }
}

Files

What ships with it

1 file beside plugin.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.

marketplace.json 553 B

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.

yesterday First seen · 12 lines scan A e5515c80048b

Subscribe to this mod's changes

chrome-devtools-mcp is a plugin published in the GitHub repository adilkalam/orca (2 stars, last pushed 1mo ago), licensed MIT. 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. It is 89% identical to chrome-devtools-mcp, differing in 6 lines, and is treated as a copy.

Browser automation Debugging Productivity

chrome-devtools-mcp

Getting it into your agent

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What ships with it

What this file has done since we first saw it

Other plugins, from other repositories

cli

hhru

dhm

kernel-sdks

webmcpify

realbrowser