io.github.developerz-ai/ui-debugger-mcp vs io.github.dynamicupgrade/chromedebug
io.github.developerz-ai/ui-debugger-mcp is an MCP server published by developerz-ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dynamicupgrade/chromedebug is an MCP server published by dynamicupgrade. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.developerz-ai/ui-debugger-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.9.0 Downloads/month (npm): 310 Downloads/week (npm): 58 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 2.9.6 Downloads/month (npm): 2 585 Downloads/week (npm): 730 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 | io.github.developerz-ai/ui-debugger-mcp | io.github.dynamicupgrade/chromedebug |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@developerz.ai/ui-debugger-mcp) | On your machine (@dynamicu/chromedebug-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/developerz-ai/ui-debugger-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.developerz-ai/ui-debugger-mcp
Autonomous UI debugging MCP server: an agent drives the browser/desktop, reports bugs + UX issues.
io.github.dynamicupgrade/chromedebug
Record browser bugs - frames, clicks and console logs - and hand them to your AI over MCP.
How to run each
io.github.developerz-ai/ui-debugger-mcp As a local MCP server: npm package
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio ui-debugger-mcp -- npx -y @developerz.ai/ui-debugger-mcpRequires: OPENAI_API_KEY (secret)
io.github.dynamicupgrade/chromedebug As a local MCP server: npm package
claude mcp add --transport stdio chromedebug -- npx -y @dynamicu/chromedebug-mcpCommands 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
The marketplaces of io.github.dynamicupgrade/chromedebug publish no settings it asks for, so we do not compare settings.
What it can do: io.github.developerz-ai/ui-debugger-mcp · What it can do: io.github.dynamicupgrade/chromedebug · Compare two other plugins
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.