wavedash vs Summer Engine
wavedash is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
wavedash is a plugin bundle for AI coding tools published by Wavedash. No marketplace we read lists it any more. Summer Engine is an MCP server published by SummerEngine. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-25. 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
| Marketplace | ||
|---|---|---|
| Community marketplace wvdsh/ai | Removed on 2026-10-16 Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.5.0 Forks (GitHub): 8 Stars (GitHub): 88 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 2.5.1 Forks (GitHub): 8 Stars (GitHub): 88 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 | wavedashno longer listed · | Summer Engine |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 2 | 88 |
| Forks (GitHub) (differs) | 0 | 8 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (mcp.wavedash.com/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | 2 | 83 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/wvdsh/ai | github.com/summerengine/summer |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-14 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 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 wavedash
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Build browser games on gamedev.pl from your coding agent.
-
Complete game development plugin — 25 skills, 7 commands, 3 agents, 5 hooks. Genre-agnostic patterns for any game type.
-
Game-development skills library for coding agents.
-
Unity's official plugin for Claude Code, with curated skills for game development, monetization, and performance optimization.
-
MCP automation loop with 167 tested tools for Godot 4
-
Build, version, review, and export websites, web apps, and games from a conversation.
What each says it does
wavedash
Build browser games, integrate the Wavedash SDK, and prepare builds for upload and publishing.
Summer Engine
The game engine built for AI. Any agent makes a multiplayer game and publishes it.
How to run each
wavedash
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Summer Engine As a remote MCP server
claude mcp add --transport http summer https://mcp.summerengine.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Summer Engine 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: wavedash · What it can do: Summer Engine · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.