Control a real Chrome browser to complete any task: fill forms, extract data, book flights.
Nothing to run from here
Chromedebug is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
81/100
trust score
199
downloads a day
local
runs on your machine
3k
downloads in 30d
What it does
ChromeDebug MCP - MCP server that provides full control over a Chrome browser instance for debugging and automation with AI assistants like Claude Code
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user chromedebug-mcp '--' npx -y @dynamicu/chromedebug-mcp
# 2 — ask your agent for something these tools do
# launch_chrome, connect_to_existing_chrome, navigate_to and 34 more
Chromedebug costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DYAll 1 server
@dynamicu1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Chromedebug as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user chromedebug-mcp '--' npx -y @dynamicu/chromedebug-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
37 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Launch a Chrome browser instance for this MCP server
No parameter schema on file.
Connect to an existing Chrome instance with debugging enabled
No parameter schema on file.
Navigate to a URL
No parameter schema on file.
Pause Chrome execution
No parameter schema on file.
Resume Chrome execution
No parameter schema on file.
Step over in Chrome debugger
No parameter schema on file.
Evaluate a JavaScript expression in Chrome
No parameter schema on file.
Get scope variables from the top call frame
No parameter schema on file.
Set a breakpoint at a specific URL and line
No parameter schema on file.
Get recent console logs
No parameter schema on file.
Check if Chrome is connected
No parameter schema on file.
Force reset Chrome by killing all processes and clearing state
No parameter schema on file.
Take a screenshot optimized for AI processing
No parameter schema on file.
Get the content of the current page including text, HTML, and DOM structure. Useful for checking if specific content exists without taking a screenshot.
No parameter schema on file.
Get information about the currently selected element from Chrome extension
No parameter schema on file.
Apply CSS styles to the currently selected element
No parameter schema on file.
Execute JavaScript code on the currently selected element
No parameter schema on file.
Clear the currently selected element
No parameter schema on file.
Get WebSocket server information for Chrome extension
No parameter schema on file.
Get a complete workflow recording including actions and optional logs
No parameter schema on file.
List all workflow recordings stored in the database
No parameter schema on file.
Get only function execution traces from a workflow recording
No parameter schema on file.
Get only error logs and error-related actions from a workflow
No parameter schema on file.
Get a concise summary of a workflow recording
No parameter schema on file.
Get filtered workflow actions by type or time range
No parameter schema on file.
Save a restore point for the current browser state including DOM, form values, storage, and cookies
No parameter schema on file.
Restore the browser to a previously saved restore point
No parameter schema on file.
List all restore points for a workflow
No parameter schema on file.
Display frame recording information in a compact format optimized for MCP tools. Shows frame metadata, console logs, and timestamps without including large image data.
No parameter schema on file.
Get information about a frame capture session including total frames and timestamps
No parameter schema on file.
Get all user interactions (clicks, inputs, keypresses, scrolls) recorded during a screen recording session
No parameter schema on file.
Get a specific frame from a frame capture session
No parameter schema on file.
Search for specific logs across all frames in a recording session
No parameter schema on file.
Get logs for a specific frame with pagination to handle large log volumes
No parameter schema on file.
Get the screenshot image data for a specific frame as base64 encoded string. This allows viewing of the actual screenshots captured during frame recordings.
No parameter schema on file.
Play a workflow recording by executing all recorded actions
No parameter schema on file.
Play a workflow recording by its name
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Chromedebug or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
BTrust score 81 / 100
Release 2.9.6 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score89
Client score81
Findings14 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationnone
Surface digest099bd325d8e5d18bfc6a99575cd53070d94e0ac73b540748acb6f26c9fb8facb
Score vectorthreat 89 → client 81
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can send data / act on an external service
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest099bd325d8e5d18b
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.9.6. Pin a release below and the command asks for exactly that one.
2.9.6
12 Oct 2026
latestNo release note was published with this version.
2.9.5
9 Oct 2026
No release note was published with this version.
2.9.3
8 Oct 2026
No release note was published with this version.
2.9.2
1 Oct 2026
No release note was published with this version.
2.9.1
23 Sep 2026
No release note was published with this version.
2.8.1
18 Sep 2026
No release note was published with this version.
2.8.0
17 Sep 2026
No release note was published with this version.
2.7.8
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Chromedebug can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.