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.
npx skills add ChromeDevTools/chrome-devtools-mcp --skill chrome-devtools-cligit 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/skills/chromedevtools/chrome-devtools-mcp/chrome-devtools-cli)<a href="https://agentmods.dev/skills/chromedevtools/chrome-devtools-mcp/chrome-devtools-cli"><img src="https://agentmods.dev/badge/skills/chromedevtools/chrome-devtools-mcp/chrome-devtools-cli/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.
<a href="https://agentmods.dev/skills/chromedevtools/chrome-devtools-mcp/chrome-devtools-cli"><img src="https://agentmods.dev/badge/skills/chromedevtools/chrome-devtools-mcp/chrome-devtools-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.02919 |
| Opus 5.5 | $0.00012 | $0.01168 |
| Sonnet 5.5 | $0.00006 | $0.00584 |
| Haiku 4.5 | $0.00003 | $0.00292 |
Grade A, and why
chrome-devtools-cli 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-cli — 100% identical, 31 lines differ
- brave-devtools-cli — 86% identical, 206 lines differ
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The chrome-devtools-mcp CLI lets you interact with the browser from your terminal.
Setup
Note: If this is your very first time using the CLI, see references/installation.md for setup. Installation is a one-time prerequisite and is not part of the regular AI workflow.
AI Workflow
- Execute: Run tools directly. If you don't know the target page's ID, run
chrome-devtools list_pagesto find it. The background server starts implicitly; do not runstart/status/stopbefore each use. - Inspect: Use
chrome-devtools take_snapshot <pageId>to get an element<uid>. - Act: Use
chrome-devtools click <pageId> <uid>,chrome-devtools fill <pageId> <uid> <value>, etc. State persists across commands.
Snapshot example:
uid=1_0 RootWebArea "Example Domain" url="https://example.com/"
uid=1_1 heading "Example Domain" level="1"
Permissions & File Access
By default, the CLI has full filesystem access (--allowUnrestrictedPaths=true), allowing file-saving parameters (--filePath, --outputDirPath) and upload_file to access files anywhere on the system. Pass --allowUnrestrictedPaths=false if you want to restrict file access to the OS temp directory.
Command Usage
chrome-devtools <tool> [arguments] [flags]
- Required arguments are passed positionally; optional arguments use flags.
- Use
--helpon any command for usage details. - Output defaults to plain Markdown-like text; pass
--output-format=jsonfor JSON.
Input Automation ( from snapshot)
chrome-devtools take_snapshot 1 # Take a text snapshot of the page to get UIDs for elements
chrome-devtools click 1 "id" # Clicks on the provided element
chrome-devtools click 1 "id" --dblClick true --includeSnapshot true # Double clicks and returns a snapshot
chrome-devtools drag 1 "src" "dst" # Drag an element onto another element
chrome-devtools drag 1 "src" "dst" --includeSnapshot true # Drag an element and return a snapshot
chrome-devtools fill 1 "id" "text" # Type text into an input, textarea, or select an option
chrome-devtools fill 1 "id" "text" --includeSnapshot true # Fill an element and return a snapshot
chrome-devtools handle_dialog 1 accept # Handle a browser dialog (accept/dismiss)
chrome-devtools handle_dialog 1 dismiss --promptText "hi" # Dismiss a dialog with prompt text
chrome-devtools hover 1 "id" # Hover over the provided element
chrome-devtools hover 1 "id" --includeSnapshot true # Hover over an element and return a snapshot
chrome-devtools press_key 1 "Enter" # Press a key or key combination ("Control+A", "Escape")
chrome-devtools press_key 1 "Control+A" --includeSnapshot true # Press a key and return a snapshot
chrome-devtools type_text 1 "hello" # Type text using keyboard into a focused input
chrome-devtools type_text 1 "hello" --submitKey "Enter" # Type text and press a submit key
chrome-devtools upload_file 1 "id" "file.txt" # Upload a file through a provided element
chrome-devtools upload_file 1 "id" "file.txt" --includeSnapshot true # Upload a file and return a snapshot
What ships with it
1 file beside SKILL.md 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.
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 Changed 6e55a0a67f66
- 2d ago Changed · +2 lines e5ef6df207c3
- 8d ago Changed 433e1148b288
- 14d ago Changed · +1 lines 5b675ec7daef
- 21d ago Changed a612e9274965
- 1mo ago Changed · +2 lines c16bb00d0584
- 1mo ago First seen · 193 lines · 31 tokens per session scan A 46be445e0fcf
chrome-devtools-cli is a skill published in the GitHub repository ChromeDevTools/chrome-devtools-mcp (53,607 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 2,919 once invoked, about $0.0001 per session on Opus 5.5. 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-08-30.
Other skills, from other repositories
devcdp
How to debug a running web app with the DevCDP tools - connect to a tab, reload to capture, drive the page with the ui tools, set breakpoints that bind, and hand off to the user. Use whenever DevCDP tools are available and the task involves a web page, the browser, console or network output, or a front-end bug.
brave-devtools
Uses Brave DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
cookie-debugging
Uses Brave DevTools MCP for inspecting, debugging, and testing cookies, session state, authentication issues, and cookie consent compliance. Use when diagnosing 401/403 errors, authentication redirects, session expiration, Cookie/Set-Cookie header issues, cookie banner consent conformance, or third-party…
a11y-debugging
Uses Brave DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
chrome-bridge
Recipes for the user's real, logged-in Chrome through the chrome-bridge MCP tools and the zero-token chrome-bridge CLI. Use when a browser task needs a multi-step recipe — a form "until the email arrives", a checkout with a test card, a pixel/GTM check, a cookie-banner audit, redirects after a migration, a page…