PWA Debug Layer
Let your coding agent inspect service workers, caches, installability, and framework-specific PWA state in your real browser instead of guessing from logs.
Overview
PWA Debug Layer is an MCP server for the Ship phase that exposes live progressive web app diagnostics—service workers, caches, installability, and framework state—from your real browser to your agent.
What is this MCP server?
- Exposes service worker registration, lifecycle, and cache contents over MCP from the browser you already use
- Surfaces installability criteria and common PWA checklist gaps without opening DevTools panels manually
- Reads framework-relevant PWA state so agents can reason about Next, Vite, or other stacks in context
- stdio npm package @aryanduntley/pwa-debug v0.1.5 for Claude Code, Cursor, and other MCP clients
- Server version 0.1.5 on npm as @aryanduntley/pwa-debug
- stdio transport per MCP server schema 2025-12-11
What problem does it solve?
Agents cannot see what the browser actually registered for your PWA, so they recommend cache busting and manifest tweaks blindly while install and offline bugs persist.
Who is it for?
Solo builders shipping PWAs who want agent-guided debugging tied to real service worker and cache data during pre-launch checks.
Skip if: Teams that only need static Lighthouse PDFs or who are not building installable or offline-capable web apps.
What do I get? / Deliverables
After you register the server, your agent can read concrete PWA runtime state and give targeted fixes for workers, caches, and installability.
- Agent-readable reports on service worker and cache state
- Installability and PWA health signals pulled from the live browser
- Actionable fix suggestions grounded in runtime diagnostics
Recommended MCP Servers
Journey fit
PWA failures usually surface during pre-launch verification when install prompts, offline behavior, and caches must work in a real browser session. Testing is the canonical shelf because this server is aimed at interactive debugging and validation, not scaffolding a new UI from scratch.
How it compares
Browser-attached PWA diagnostics MCP, not a Lighthouse-only CLI or a manifest generator skill.
Common Questions / FAQ
Who is PWA Debug Layer for?
Indie and solo developers using Claude Code, Cursor, or similar MCP clients who are building PWAs and need runtime truth from the browser during testing.
When should I use PWA Debug Layer?
Use it when install prompts fail, stale caches break updates, or offline mode misbehaves and you want the agent to inspect live worker and cache state before you ship.
How do I add PWA Debug Layer to my agent?
Install @aryanduntley/pwa-debug from npm, add a stdio MCP server entry pointing at that package in your client config, then reload the client with your PWA open in the browser the layer attaches to.