pwa-debug vs Baton
pwa-debug is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
pwa-debug is a plugin bundle for AI coding tools published by aryanduntley. No marketplace we read lists it any more. Baton is an MCP server published by kanumuri9593. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Baton | |
|---|---|---|
| Community marketplace aryanduntley/pwa-debug-layer | Removed on 2026-10-15 Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.10 Downloads/month (npm): 645 Downloads/week (npm): 442 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | pwa-debugno longer listed · | Baton |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | On your machine (@aryanduntley/pwa-debug) | On your machine (baton-run) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/aryanduntley/pwa-debug-layer | github.com/kanumuri9593/baton |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of pwa-debug
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
MCP server for Chrome DevTools
-
Inspect and debug Android and iOS apps with the mobile-debug-mcp server.
-
Live browser debugging for AI assistants — DOM, console, network via MCP.
-
Diagnose and fix Firefox DevTools MCP setup issues. Use this if the firefox-devtools-mcp plugin is not working.
-
Debug PWAs in your real browser via MCP: service-worker, cache, installability & framework state.
-
MCP server and CLI for Brave DevTools
What each says it does
pwa-debug
Browser-side debug layer that exposes live PWA state (DOM, framework state, stores, events, library popups) to AI agents via MCP. Pairs with the optional chrome-devtools-mcp (registered separately); the bundled chrome-devtools-coexistence skill walks Claude through adding it.
Baton
Run, hot-reload and screenshot Flutter, web, React Native and native iOS/Android apps.
How to run each
pwa-debug
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Baton As a local MCP server: npm package
claude mcp add --transport stdio baton -- npx -y baton-runCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: pwa-debug · What it can do: Baton · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.