mcpbeat Sign in

PWA Debug Layer MCP Server

local only

PWA Debug Layer runs on your own machine — the client starts it, so there is no endpoint to ping. 94 installs a week from npm. Last commit 1 Nov 2026.

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

Installs per day peak 47 · avg 7 · +370% w/w
a month agotoday
94
Installs / week
npm · @aryanduntley/pwa-debug
0
Stars
0 open issues
1 Nov 2026
Last commit
1 release in 90 days
MIT
License
TypeScript

What the code does

We read the source, 4 h ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    execFile(adbPath, [...args], { timeout: timeoutMs, maxBuffer: 8 * 1024 * 1024 }, (err, stdout, stderr) => {
Reads files and sends them to the network packages/host/src/browser_launch/node_deps.ts:11
  readdirSync,
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    compiled = new Function(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add pwa-debug-layer -- npx -y @aryanduntley/pwa-debug
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "pwa-debug-layer": {
      "command": "npx",
      "args": [
        "-y",
        "@aryanduntley/pwa-debug"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.pwa-debug-layer]
command = "npx"
args = ["-y", "@aryanduntley/pwa-debug"]
.cursor/mcp.json
{
  "mcpServers": {
    "pwa-debug-layer": {
      "command": "npx",
      "args": [
        "-y",
        "@aryanduntley/pwa-debug"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pwa-debug-layer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@aryanduntley/pwa-debug"
      ]
    }
  }
}

Alternatives to PWA Debug Layer

same job, measured the same way
D
Dropcoin A11y
by freshfos

Accessibility pre-checks (WCAG/BFSG) in a real browser + statement drafts. Pay per call.

2 tools answering
Browsentic
by imshaikot

Agentic browser harness: your agent CLI in your real, signed-in browser, from a side panel or MCP.

541 installs/wk local only
Usable Browser Agent
by savvy-tech-sphere

MCP server and Firefox add-on that let an AI agent drive your real, logged-in browser. Free tier.

46 installs/wk local only
WebLoom
by webloomhq

104 tools: drive YOUR real Chrome via CDP + browse/install/publish Threads in chat. webloom.run.

local only
Feedthrough
by feedthrough

Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.

127 installs/wk local only
Banned from Equestria MCP
by rocnubie

Play Banned from Equestria Daily online in your browser with the self-hosted Ruffle player, version

local only
Uplink
by uplink

Automate a real, logged-in browser on your own device — no stored credentials, no bot detection.

94 installs/wk local only
voicehook
by voicehook-ai

Talk with your agents. A voice call in the browser that your agent can start or join.

21 tools answering

PWA Debug Layer — questions

Answers built from our own checks of this server.

Why is there no uptime for PWA Debug Layer?
PWA Debug Layer runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @aryanduntley/pwa-debug was installed 94 times last week.
How do I connect PWA Debug Layer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @aryanduntley/pwa-debug straight from npm; nothing to host, nothing to sign up for.
How many people use PWA Debug Layer?
The npm package @aryanduntley/pwa-debug was installed 94 times in the last week. Week over week that is +370%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is PWA Debug Layer open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.