Ext Ops Panel
Open dashboard
Comparison

waves-exovian vs Wavedash

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). Wavedash is an MCP server published by wvdsh. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
Marketplacewaves-exovianWavedash
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.1.0
Forks (GitHub): 0
Stars (GitHub): 2
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

waves-exovian vs Wavedash
Factwaves-exovianWavedash
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.wavedash.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)16Not published
Parts of the bundle (differs)54Not a bundle
Licence (differs)AGPL-3.0-or-laterNot stated
Repository (differs)github.com/exovian-developments/waves-cowork-plugingithub.com/wvdsh/ai
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

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

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

Wavedash

In its own words, on Official MCP Registry:

Wavedash docs and workflow guidance for building and publishing browser games.

How to run each

waves-exovian As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install waves-exovian@claude-community

Wavedash As a remote MCP server

Claude Code
claude mcp add --transport http wavedash https://mcp.wavedash.com/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: waves-exovian · What it can do: Wavedash · 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