Pwa Debug Layer

Name: Pwa Debug Layer
Author: aryanduntley

by aryanduntleycommunityv0.2.0

An MCP server and companion browser extension for debugging PWAs and modern web apps against a real, logged-in Chromium browser profile. It exposes live runtime data such as DOM, console, network, framework/store state, service workers, caches, storage, and installability diagnostics, and supports direct interaction with the page.

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

GitHub Repository

Install & configure

Prerequisites

required
Install Node.js
Node.js 20.19 or newer is required.
required
Use an MCP-aware client
You need an MCP-compatible client such as Claude Code.
https://docs.claude.com/en/docs/claude-code
required
Install a supported Chromium-family browser
Use a Chromium-family browser. Snap-installed browsers are not supported for the native-messaging host. Native package installs are recommended.
required
If using the published plugin/package path, have npx available
The simplest install path uses the published npm package via npx, which comes with Node.js/npm.
optional
If using a local build instead, install pnpm and build the repo
Alternative local install path: install pnpm, clone the repository, run pnpm install, pnpm build, and load the unpacked extension from packages/extension/dist/.
```
$ git clone https://github.com/<your-fork>/pwa-debug-layer && cd pwa-debug-layer && pnpm install && pnpm build
```
required
Load the browser extension
The browser extension must be installed in your Chromium-family browser. With the published package/plugin flow, use the server tools such as pdl_install_extension or the launch/setup flow to install or preload it. In some browsers/versions this can be preloaded automatically; in others a one-time manual 'Load unpacked' step is required.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `pwa-debug-layer` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js** — Node.js 20.19 or newer is required.
- **Use an MCP-aware client** — You need an MCP-compatible client such as Claude Code. (https://docs.claude.com/en/docs/claude-code)
- **Install a supported Chromium-family browser** — Use a Chromium-family browser. Snap-installed browsers are not supported for the native-messaging host. Native package installs are recommended.
- **If using the published plugin/package path, have npx available** — The simplest install path uses the published npm package via npx, which comes with Node.js/npm.
- **Load the browser extension** — The browser extension must be installed in your Chromium-family browser. With the published package/plugin flow, use the server tools such as pdl_install_extension or the launch/setup flow to install or preload it. In some browsers/versions this can be preloaded automatically; in others a one-time manual 'Load unpacked' step is required.

Optional prerequisites:
- If using a local build instead, install pnpm and build the repo — Alternative local install path: install pnpm, clone the repository, run pnpm install, pnpm build, and load the unpacked extension from packages/extension/dist/. Run: `git clone https://github.com/<your-fork>/pwa-debug-layer && cd pwa-debug-layer && pnpm install && pnpm build`

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@aryanduntley/pwa-debug@latest"]

Note: Preferred install path is the published npm package via npx, as documented by the Claude Code plugin section. The server itself is stdio. After adding the MCP server, additional interactive setup is required: register the native host/extension with the provided MCP tools (for example host_register_extension / pdl_check_setup / pdl_install_extension / pdl_launch_browser). A local-build alternative also exists: command `node` with args [`/absolute/path/to/pwa-debug-layer/packages/host/dist/main.js`]. No environment variables were documented for the MCP server command.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Preferred install path is the published npm package via npx, as documented by the Claude Code plugin section. The server itself is stdio. After adding the MCP server, additional interactive setup is required: register the native host/extension with the provided MCP tools (for example host_register_extension / pdl_check_setup / pdl_install_extension / pdl_launch_browser). A local-build alternative also exists: command `node` with args [`/absolute/path/to/pwa-debug-layer/packages/host/dist/main.js`]. No environment variables were documented for the MCP server command.