What is chrome-devtools?

A connection that lets a coding agent inspect and automate a live Google Chrome browser through its developer tools. Chrome developer tools expose information such as page performance, network requests, and console messages.

It helps investigate browser errors, inspect network activity, analyse performance traces, and automate actions in an open Chrome instance.

It gives the agent direct visibility into what a running web page is doing, which is difficult to determine from source code alone.

chrome-devtools — MCP server by chicogong

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.

agentmods

npx agentmods add mcp/chicogong/codepod/chrome-devtools

Clone the repo

git clone --depth 1 https://github.com/chicogong/codepod

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

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 88% copy Near-identical to another mod in the catalogue.

Security

Grade A, and why

chrome-devtools 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

88% identical to chrome-devtools — 3 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.json · 10 lines

What it actually says

{
  "chrome-devtools": {
    "command": "npx",
    "args": [
      "-y",
      "chrome-devtools-mcp@latest"
    ],
    "env": {}
  }
}

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 · 10 lines scan A 97b1149abd5b

Subscribe to this mod's changes

chrome-devtools is an MCP server published in the GitHub repository chicogong/codepod (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 88% identical to chrome-devtools, differing in 3 lines, and is treated as a copy.

Browser automation Languages Research ai-assistant chatgpt-alternative claude claude-code desktop-app rust

chrome-devtools

Getting it into your agent

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

pushengage-mcp

browser

comms

antigravity-browser-bridge

codegraph

shadcn