Ext Ops Panel
Open dashboard
Comparison

Summer Engine vs Wavedash

Summer Engine is an MCP server published by SummerEngine. Marketplaces we read that list it: 2 (Official MCP Registry, 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-16. 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
MarketplaceSummer EngineWavedash
Official MCP Registry Listed
Version: 4.3.0
Forks (GitHub): 6
Stars (GitHub): 77
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 2.5.1
Forks (GitHub): 6
Stars (GitHub): 77
Not marked · First seen
Not listed

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

Summer Engine vs Wavedash
FactSummer EngineWavedash
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)77 (better)2 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last release (differs)2026-10-16Not published
Where it runs (differs)Remote server or your machineRemote server (mcp.wavedash.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)83Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/summerengine/summergithub.com/wvdsh/ai
Changes in the last 7 days (differs)50
First seen (differs)2026-10-122026-10-11
Endpoint at the last checknot checked yetnot 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

Summer Engine

In its own words, on Official MCP Registry:

The game engine built for AI. Any agent makes a multiplayer game and publishes it.

Wavedash

In its own words, on Official MCP Registry:

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

How to run each

Summer Engine As a remote MCP server

Claude Code
claude mcp add --transport http summer https://mcp.summerengine.com/mcp

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: Summer Engine · What it can do: Wavedash · Compare two other plugins

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.

Where the data comes from: how the catalog is built