Ext Ops Panel
Open dashboard
Comparison

mushi-debugger vs SnagRelay

mushi-debugger is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.

mushi-debugger is a plugin bundle for AI coding tools published by kensaurus. No marketplace we read lists it any more. SnagRelay is an MCP server published by snagrelay.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
Marketplacemushi-debuggerSnagRelay
Community marketplace kensaurus/mushi-mushi Removed on 2026-10-17
Version: 1.0.2
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

mushi-debugger vs SnagRelay
Factmushi-debuggerno longer listed · SnagRelay
Marketplaces that list it (differs)01
Stars (GitHub) (differs)30
Forks (GitHub) (differs)20
Last releaseNot publishedNot published
Where it runs (differs)Remote server (kensaur.us/mushi-mushi/hosted-mcp)Remote server (mcp.snagrelay.com/v1)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/kensaurus/mushi-mushigithub.com/snagrelay/agent-plugin
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-12
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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 mushi-debugger

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • lightrun

    Lightrun's runtime investigation toolkit for Claude Code. Guides deterministic, evidence-first debugging of live applications by capturing real production behavior — variable…

    by lightrun-platform · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • BugScreen

    Configure mobile bug reporting and investigate retained reports with your coding assistant.

    by bugscreen.app · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • debug-session

    Ask Claude Code to help you debug an issue

    by Anand Tyagi · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • debug-detective

    DevsForge Bug Detective tool for streamlined Bug Detective processes and enhanced productivity.

    by DevsForge Community · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • debugging-toolkit

    Interactive debugging, developer experience optimization, and smart debugging workflows

    by Seth Hobson · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • debugging-toolkit

    Interactive debugging, developer experience optimization, and smart debugging workflows

    by Seth Hobson · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

mushi-debugger

In its own words, on Community GitHub marketplaces:

Triage and fix Mushi bug reports without leaving Claude Code: hosted MCP (OAuth sign-in, no keys) + a mushi-debugger subagent that pulls reports, diagnosis, and fix context

SnagRelay

In its own words, on Official MCP Registry:

Bug reports your coding agent can fix: real element, console errors, failing requests with bodies.

How to run each

mushi-debugger

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

SnagRelay As a remote MCP server

Claude Code
claude mcp add --transport http snagrelay https://mcp.snagrelay.com/v1

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only SnagRelay has a remote endpoint we check. How we check endpoints

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: mushi-debugger · What it can do: SnagRelay · 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.

Where the data comes from: how the catalog is built