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 memory-leak-debugginggit 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/memory-leak-debugging)<a href="https://agentmods.dev/skills/chromedevtools/chrome-devtools-mcp/memory-leak-debugging"><img src="https://agentmods.dev/badge/skills/chromedevtools/chrome-devtools-mcp/memory-leak-debugging/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/memory-leak-debugging"><img src="https://agentmods.dev/badge/skills/chromedevtools/chrome-devtools-mcp/memory-leak-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 12 Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.Fix: Remove all code or instructions that read MCP configuration files (mcp.json). MCP server details should be managed by the agent runtime, not read by individual skills.
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.00052 | $0.00933 |
| Opus 5.5 | $0.00021 | $0.00373 |
| Sonnet 5.5 | $0.00010 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade B, and why
memory-leak-debugging scanned grade B with 1 finding 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
Advanced memory debugging tools (`compare_heapsnapshots`, `get_heapsnapshot_details`, etc.) are only available when the server is started with the `--memoryDebugging` flag. First check if these tools are available; if no Copies of this mod
2 near-identical copies found in the catalogue:
- memory-leak-debugging — 100% identical, 0 lines differ
- memory-leak-debugging — 86% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Leak Debugging
This skill provides expert guidance and workflows for finding, diagnosing, and fixing memory leaks in JavaScript and Node.js applications using Chrome DevTools MCP tools.
Prerequisites
Advanced memory debugging tools (compare_heapsnapshots, get_heapsnapshot_details, etc.) are only available when the server is started with the --memoryDebugging flag. First check if these tools are available; if not, try to read the MCP configuration file to check if --memoryDebugging is enabled.
Core Principles
- Prefer MCP memory tools: Do NOT attempt to read raw
.heapsnapshotfiles directly, as they are extremely large and will consume too many tokens. Use the Chrome DevTools MCP heap snapshot tools to summarize, compare, and inspect snapshots. - Isolate the Leak: Determine if the leak is in the browser (client-side) or Node.js (server-side).
- Common Culprits: Look for detached DOM nodes, unhandled closures, global variables, event listeners not being removed, and caches growing unbounded. Note: Detached DOM nodes are sometimes intentional caches; always ask the user before nulling them.
- Close Loaded Snapshots: Heap snapshots can be large. After completing an investigation, use
close_heapsnapshotfor each loaded snapshot to release memory held by the MCP server.
Workflows
1. Capturing Snapshots
When investigating a frontend web application memory leak, utilize the chrome-devtools-mcp tools to interact with the application and take snapshots.
- Use page-scoped tools like
click,navigate_page,fill, etc. (specifyingpageId) to manipulate the page into the desired state. - Revert the page back to the original state after interactions to see if memory is released.
- Repeat the same user interactions 10 times to amplify the leak.
- Use
take_heapsnapshot(withpageId) to save.heapsnapshotfiles to disk at baseline, target (after actions), and final (after reverting actions) states.
2. Comparing Snapshots
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.
- 1mo ago First seen · 59 lines · 52 tokens per session scan B 895127ac55a3
memory-leak-debugging is a skill published in the GitHub repository ChromeDevTools/chrome-devtools-mcp (53,865 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 933 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). 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…