MCP.Market

PWA Debug Layer MCP server

by aryanduntley·io.github.aryanduntley/pwa-debug-layer·v1.2.0
No reviews yet

Debug PWAs in your real browser via MCP: service-worker, cache, installability & framework state.

B74/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B74/100

not scanned yet

Adoption
New

0 stars61 downloads/wk

Reviews

Write one

Nobody has reviewed PWA Debug Layer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PWA Debug Layer tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How PWA Debug Layer compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
74/100
higher than 40% of 866 Scraping and browsing servers
Downloads a week
61
more than 43% of 309 Scraping and browsing servers with a package

Release history: 3 versions in the registry since 2026-06-26, latest 2026-11-02, typically one every 128 days.

Install PWA Debug Layer in Claude Code, Cursor or VS Code

Runs npx -y @aryanduntley/pwa-debug on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pwa-debug-layer -- npx -y @aryanduntley/pwa-debug
Add to Cursor

What the publisher says

From the PWA Debug Layer repository's README, as published. We do not edit it. Read it on GitHub

pwa-debug-layer

An AI-native debugging layer for PWAs and modern web apps. It lets an AI agent (e.g. Claude Code via MCP) see and act on your live, logged-in browser the way a developer with full DevTools open would — DOM, console, network, framework state, store state, service workers, caches, and direct interaction — as structured data the model consumes natively.

It's built for the questions developers actually search for and that Chrome DevTools makes you assemble by hand: why won't my service worker update? why is my cache stale? why won't my PWA install? why does this component have the wrong state? — answered by an agent reading the runtime directly, against your real browser profile (extensions, auth, and all), not a sterile automated tab.

What it answers

The PWA failures developers actually search for, read straight from your live runtime:

  • Why won't my service worker update? Why are some users on old code? — SW lifecycle with waiting-vs-active versions, plus an update-propagation / version-skew analyzer.
  • Why is my cache stale? Why are chunks 404ing after a deploy? — CacheStorage contents with age, and a cached-HTML-vs-JS skew check.
  • Why won't my PWA install? — structured installability diagnostics with per-gap remediation, not just "manifest invalid."
  • What's actually in IndexedDB / localStorage right now? — live storage inspection (inspect IndexedDB live).
  • What can this browser actually do? — a live capability matrix (Push / Background Sync / Periodic Sync / Badging / File System Access / Window Controls Overlay).

All read from your real, logged-in profile — service-worker, cache, and extension state included — which chrome-devtools-mcp's sterile automated Chrome can't see.

The goal is to eliminate the "user is the AI's eyes and hands" loop. Today, debugging a PWA with AI usually means the human copy/pastes DOM snippets, describes console errors, screenshots UI state, and hand-executes clicks. This project replaces that with direct, structured access.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PWA Debug Layer: common questions

Is PWA Debug Layer MCP server safe?
Mostly: it is graded B (74/100). Read the PWA Debug Layer safety report
How do I install PWA Debug Layer?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does PWA Debug Layer need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is PWA Debug Layer maintained?
The last commit was 132 days ago (2026-06-26). The latest release is v1.2.0.
What can I use instead of PWA Debug Layer?
Servers from other publishers that do the same job: Web Browser (kogiQA) MCP server, GrowBlocks Dev Kit MCP server and SeleniumBase MCP server.
How does PWA Debug Layer compare with other Scraping and browsing MCP servers?
safety score 74/100 (higher than 40% of 866 Scraping and browsing servers); downloads a week 61 (more than 43% of 309 Scraping and browsing servers with a package). Full comparison.

Alternatives to PWA Debug Layer

Same job from other publishers: the closest match first, then the best rated.

  • Web Browser (kogiQA)
    This web browser has been designed to help your agent debug and develop complex web applications.
    C
  • GrowBlocks Dev Kit
    Build, play-test with screenshots, and ship three.js browser games on GrowBlocks.
    A
  • SeleniumBase MCP
    Stealthy browser automation, testing, and web-scraping via CDP Mode.
    A
  • Next AI Draw.io
    draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
    A
  • AIHawk
    AI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.
    More from feder-cr →
    A