Control a real Chrome browser to complete any task: fill forms, extract data, book flights.
Nothing to run from here
Playwright Debug 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.
93/100
trust score
2
downloads a day
local
runs on your machine
40
downloads in 30d
What it does
MCP server for frontend debugging with Playwright - Debug web apps with AI assistance
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user playwright-debug-mcp '--' npx -y playwright-debug-mcp
# 2 — ask your agent for something these tools do
# click, fill, select and 60 more
Playwright Debug costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LAAll 2 servers
lars-albinsson2 servers
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 Playwright Debug 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 playwright-debug-mcp '--' npx -y playwright-debug-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
63 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.
Click on an element matching the given selector
No parameter schema on file.
Fill a form field with the given value. Clears existing content first.
No parameter schema on file.
Select option(s) from a dropdown/select element
No parameter schema on file.
Scroll the page or scroll an element into view
No parameter schema on file.
Wait for an element to appear/disappear or for navigation to a URL
No parameter schema on file.
Hover over an element
No parameter schema on file.
Go back to the previous page in browser history
No parameter schema on file.
Go forward to the next page in browser history
No parameter schema on file.
Reload the current page
No parameter schema on file.
Get console log entries from the page. Useful for seeing errors, warnings, and debug output.
No parameter schema on file.
Clear captured console logs
No parameter schema on file.
Get network request log. See API calls, their status codes, and timing. Essential for debugging Lambda/API issues.
No parameter schema on file.
Get detailed info about a specific network request including headers
No parameter schema on file.
Clear captured network logs
No parameter schema on file.
Get a summarized DOM tree. Returns tag names, IDs, classes, and text content in a digestible format.
No parameter schema on file.
Get detailed information about a specific element including computed styles and bounding box
No parameter schema on file.
Get visible text content of elements matching a selector
No parameter schema on file.
Take a screenshot of the page or a specific element. Returns base64 PNG image.
No parameter schema on file.
Execute arbitrary JavaScript in the page context. Powerful for custom inspection and debugging.
No parameter schema on file.
Get the React component tree with props and state. Works with React 16+.
No parameter schema on file.
Find React components by name. Returns matching components with their props and state.
No parameter schema on file.
Get detailed state and props for a specific React component
No parameter schema on file.
Collect all instances of a React component type with props→HTML mapping. Useful for understanding component behavior, comparing different usages, or extracting component patterns. Returns props, rendered HTML, and minified source for each instance.
No parameter schema on file.
Inspect Redux store state and recent actions. Works with Redux DevTools or globally exposed stores.
No parameter schema on file.
Inspect Zustand store state. Finds stores used in React components.
No parameter schema on file.
Inspect React Query/TanStack Query cache. Shows queries, their status, and cached data.
No parameter schema on file.
List all React Context providers and their current values.
No parameter schema on file.
Track component render counts to identify unnecessary re-renders.
No parameter schema on file.
Find React components with slow render times. Requires React Profiler or DevTools.
No parameter schema on file.
Get Core Web Vitals (LCP, FID, CLS) and other performance metrics.
No parameter schema on file.
Detect SSR hydration mismatches. Essential for Next.js/Remix debugging.
No parameter schema on file.
Find React error boundaries and any errors they have caught.
No parameter schema on file.
Detect potential memory leaks: large DOM, detached nodes, growing collections.
No parameter schema on file.
Run accessibility audit: missing alt text, labels, heading structure, color contrast, ARIA issues.
No parameter schema on file.
Get the accessibility tree showing roles, names, and states. Useful for screen reader debugging.
No parameter schema on file.
Analyze a console error with full context: related network requests, React state, and debugging suggestions. Best tool for diagnosing issues.
No parameter schema on file.
Get a quick overview of the debugging state: page info, error count, failed requests
No parameter schema on file.
Get a token-efficient accessibility snapshot of the page (YAML). Best first tool for understanding page structure — much cheaper than screenshots or DOM dumps.
No parameter schema on file.
Save the current page as a PDF file (requires headless mode).
No parameter schema on file.
List all open browser tabs with their URLs and titles.
No parameter schema on file.
Open a new browser tab, optionally navigating to a URL. The new tab becomes active.
No parameter schema on file.
Switch the active tab. Subsequent tools target the selected tab.
No parameter schema on file.
Close a tab (default: the active tab).
No parameter schema on file.
Configure how alert/confirm/prompt dialogs are answered (default: dismiss). Set before triggering the dialog.
No parameter schema on file.
Get the log of dialogs (alert/confirm/prompt) that appeared and how they were handled.
No parameter schema on file.
Set files on a file input element (<input type=
No parameter schema on file.
List files downloaded during this session with their saved paths.
No parameter schema on file.
Press a keyboard key (e.g. Enter, Escape, Tab, ArrowDown, Control+A), optionally focusing an element first.
No parameter schema on file.
Drag one element onto another (drag and drop).
No parameter schema on file.
Get browser cookies for the current context.
No parameter schema on file.
Set a browser cookie. Useful for injecting auth/session tokens.
No parameter schema on file.
Clear all cookies in the browser context.
No parameter schema on file.
Get localStorage or sessionStorage contents of the current page.
No parameter schema on file.
Set a localStorage or sessionStorage item.
No parameter schema on file.
Clear localStorage and/or sessionStorage.
No parameter schema on file.
Resize the browser viewport.
No parameter schema on file.
Emulate a mobile/tablet device (viewport, user agent, touch). Recreates the browser context — cookies, storage, tabs, and mocks are reset; the current URL is reloaded.
No parameter schema on file.
Set the browser geolocation (grants the geolocation permission).
No parameter schema on file.
Toggle offline mode to test offline behavior and error handling.
No parameter schema on file.
Throttle network speed to test slow connections (slow-3g, fast-3g, 4g, none).
No parameter schema on file.
Throttle CPU to test performance on slow devices (rate 1 = none, 4 = 4x slowdown).
No parameter schema on file.
Navigate to a URL in the browser. Launches browser if not already running.
No parameter schema on file.
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 Playwright Debug 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: —
ATrust score 93 / 100
Release 0.2.0 · scanned 15 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 score100
Client score93
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest598bc56c6596b7eb9db87329fe7ea31b355c63cc2e480d4cf9a5ffbae51c5519
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| 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 surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (39 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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 |
|---|---|---|
| navigate | no tags | |
| click | no tags | |
| fill | no tags | |
| select | no tags | |
| scroll | no tags | |
| wait_for | no tags | |
| hover | no tags | |
| type | no tags | |
| go_back | no tags | |
| go_forward | no tags | |
| reload | no tags | |
| get_console | no tags | |
| clear_console | no tags | |
| get_network | no tags | |
| get_request_detail | no tags | |
| clear_network | no tags | |
| get_dom | no tags | |
| get_element | no tags | |
| get_text_content | no tags | |
| screenshot | no tags | |
| evaluate_js | no tags | |
| get_react_tree | no tags | |
| find_component | no tags | |
| get_component_state | no tags | |
| collect_component_instances | no tags | |
| get_redux_state | no tags | |
| get_zustand_stores | no tags | |
| get_react_query_cache | no tags | |
| get_context_values | no tags | |
| get_render_count | no tags | |
| get_slow_components | no tags | |
| get_web_vitals | no tags | |
| find_hydration_errors | no tags | |
| get_error_boundaries | no tags | |
| detect_memory_leaks | no tags | |
| audit_accessibility | no tags | |
| get_aria_tree | no tags | |
| explain_error | no tags | |
| get_debug_summary | no tags |
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 digest598bc56c6596b7eb
Scanned2026-10-15
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 0.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
undated
latestNo release note was published with this version.
—
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 Playwright Debug 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.