waves-exovian vs com.vibsync/vibsync
waves-exovian is a plugin bundle for AI coding tools published by exovian-developments. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.vibsync/vibsync is an MCP server published by vibsync.com. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 |  waves-exovian |  com.vibsync/vibsync |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 3.1.9 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.3 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 | waves-exovian | com.vibsync/vibsync |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.vibsync.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 16 | Not published |
| Parts of the bundle (differs) | 54 | 2 |
| Licence (differs) | AGPL-3.0-or-later | MIT |
| Repository (differs) | github.com/exovian-developments/waves-cowork-plugin | github.com/loosedays/vibsync-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago, requires a key |
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
waves-exovian
Waves is a product development framework that turns ideas into production software through a structured sequence of AI-driven artifacts. It provides the AI agent with persistent memory, project awareness, and a clear methodology — so every session starts informed, every task traces to a purpose, and every decision is recorded. The framework guides the complete lifecycle: validate the idea (feasibility analysis with Monte Carlo and Bayesian projections and kill criteria), distill findings into validated facts (foundation), define what the product is and why it exists (blueprint with capabilities, flows, rules, and success metrics), plan delivery in organic cycles called waves (roadmaps with phases and milestones), track implementation per task (logbooks with objectives, scope, and completion guides), execute code aligned with project rules and business intent (objectives-implement), and document what was accomplished (resolutions). Each artifact feeds the next. Each session picks up where the last one left off
com.vibsync/vibsync
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
How to run each
waves-exovian As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install waves-exovian@claude-communitycom.vibsync/vibsync As a remote MCP server
claude mcp add --transport http vibsync https://mcp.vibsync.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.vibsync/vibsync 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: waves-exovian · What it can do: com.vibsync/vibsync · 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.