Ext Ops Panel
Open dashboard
Comparison

vibe-replay vs io.github.MUSE-CODE-SPACE/vibe-coding

vibe-replay is a plugin bundle for AI coding tools published by tuo-lei. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.MUSE-CODE-SPACE/vibe-coding is an MCP server published by MUSE-CODE-SPACE. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
Marketplacevibe-replayio.github.MUSE-CODE-SPACE/vibe-coding
Claude Code: claude-plugins-community Listed
Version: 1.0.2
Forks (GitHub): 5
Stars (GitHub): 38
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.12.1
Downloads/month (npm): 209
Downloads/week (npm): 32
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

vibe-replay vs io.github.MUSE-CODE-SPACE/vibe-coding
Factvibe-replayio.github.MUSE-CODE-SPACE/vibe-coding
Marketplaces that list it11
Stars (GitHub) (differs)38 (better)1 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (vibe-coding-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/tuo-lei/vibe-replaygithub.com/muse-code-space/vibe-coding-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

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

vibe-replay

In its own words, on Claude Code: claude-plugins-community:

Turn AI coding sessions into shareable, interactive replays. Auto-generates GitHub PR artifacts (markdown + animated GIF), self-contained HTML replays, and session analytics. Supports Claude Code and Cursor.

io.github.MUSE-CODE-SPACE/vibe-coding

In its own words, on Official MCP Registry:

Auto-document vibe coding sessions - collect, summarize, and publish

How to run each

vibe-replay As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibe-replay@claude-community

io.github.MUSE-CODE-SPACE/vibe-coding As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio vibe-coding -- npx -y vibe-coding-mcp

Commands 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: vibe-replay · What it can do: io.github.MUSE-CODE-SPACE/vibe-coding · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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