PWA Debug Layer MCP Server
io.github.aryanduntley/pwa-debug-layer
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the PWA Debug Layer MCP server?
Debug PWAs in your real browser via MCP: service-worker, cache, installability & framework state.
How to install PWA Debug Layer
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"pwa-debug-layer": {
"command": "npx",
"args": [
"-y",
"@aryanduntley/pwa-debug"
]
}
}
}Related MCP servers

Database-driven FP enforcement and project management for AI-maintained codebases

Infimium
Private AI context layer for semantic code search, dependency graphs, memory, and workspaces—100% local, zero token bloat.

Marrow
Shared memory for parallel AI coding agents. Local, free, with rooms and file claims.

io.github.asadullokhn/teztun
Manage TezTun tunnels, subdomains, and service tokens from any MCP-compatible AI client.
Tells you what leaked in a .har capture, who's on the page, and what to strip. No network calls.

pgops
Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers
