chrome-devtools

chrome-devtools is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from colinhacks/zod. Its token cost is not measured, scanned A, a copy of chrome-devtools, MIT.

A connection setting for inspecting and automating a running Google Chrome browser through Chrome's developer tools interface. It can access browser performance traces, network activity, and console output.

In plain words
What is it for?
Use it to connect the agent to Chrome for browser inspection, performance tracing, network checks, and console monitoring.
Why use it?
It lets an agent examine what a live browser is doing when investigating page behavior, loading problems, or runtime messages.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Written for no agent in particular: it speaks MCP, so any client can run it. Also seen: listed in a Claude config.

Good fit Use it to connect the agent to Chrome for browser inspection, performance tracing, network checks, and console monitoring.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/colinhacks/zod/chrome-devtools

Installing this writes the configuration, not the program: `nub` has to be on your PATH already, or the server will not start.

About the project

Zod is a TypeScript library that checks whether data matches defined schemas while also deriving corresponding static types. It is used by developers to validate data at runtime in TypeScript applications.

colinhacks/zod · 44,145 stars · on GitHub · zod.dev

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/colinhacks/zod

Installing this writes the configuration, not the program: `nub` has to be on your PATH already, or the server will not start.

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

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

README.md
[![agentmods](https://agentmods.dev/badge/mcp/colinhacks/zod/chrome-devtools/github.svg)](https://agentmods.dev/mcp/colinhacks/zod/chrome-devtools)
Your own site
<a href="https://agentmods.dev/mcp/colinhacks/zod/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/colinhacks/zod/chrome-devtools/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

Your own site · 80×15
<a href="https://agentmods.dev/mcp/colinhacks/zod/chrome-devtools"><img src="https://agentmods.dev/badge/mcp/colinhacks/zod/chrome-devtools.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 100% 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 1mo ago.

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

100% identical to chrome-devtools — 9 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 · 12 lines

What it actually says

{
  "chrome-devtools": {
    "command": "nub",
    "args": [
      "dlx",
      "chrome-devtools-mcp@latest"
    ],
    "env": {
      "NODE_COMPAT": "1"
    }
  }
}
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. 1mo ago Changed · +3 lines a7464589921c
  2. 1mo ago First seen · 9 lines scan A 4f096813cf17

Subscribe to this mod's changes

chrome-devtools is an MCP server published in the GitHub repository colinhacks/zod (44,145 stars, last pushed 3d 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 100% identical to chrome-devtools, differing in 9 lines, and is treated as a copy.