io.github.MUSE-CODE-SPACE/vibe-coding vs io.github.erova/vibesharing
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). io.github.erova/vibesharing is an MCP server published by erova. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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.MUSE-CODE-SPACE/vibe-coding |  io.github.erova/vibesharing |
|---|---|---|
| Official MCP Registry | Listed Version: 2.12.1 Downloads/month (npm): 256 Downloads/week (npm): 48 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.17.0 Downloads/month (npm): 346 Downloads/week (npm): 57 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
| Fact | io.github.MUSE-CODE-SPACE/vibe-coding | io.github.erova/vibesharing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (vibe-coding-mcp) | On your machine (@vibesharingapp/mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/muse-code-space/vibe-coding-mcp | github.com/erova/vibesharing-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
io.github.MUSE-CODE-SPACE/vibe-coding
Auto-document vibe coding sessions - collect, summarize, and publish
io.github.erova/vibesharing
Deploy prototypes and collect team feedback from Claude Code, Cursor, or any MCP client.
How to run each
io.github.MUSE-CODE-SPACE/vibe-coding As a local MCP server: npm package
claude mcp add --transport stdio vibe-coding -- npx -y vibe-coding-mcpio.github.erova/vibesharing As a local MCP server: npm package
claude mcp add --env "VIBESHARING_TOKEN=<YOUR_VIBESHARING_TOKEN>" --transport stdio vibesharing -- npx -y @vibesharingapp/mcp-serverRequires: VIBESHARING_TOKEN (secret)
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
The marketplaces of io.github.MUSE-CODE-SPACE/vibe-coding publish no settings it asks for, so we do not compare settings.
What it can do: io.github.MUSE-CODE-SPACE/vibe-coding · What it can do: io.github.erova/vibesharing · 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.