Ext Ops Panel
Open dashboard
Comparison

com.spriteship/spriteship vs Summer Engine

com.spriteship/spriteship is an MCP server published by spriteship.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-21. 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
Marketplacecom.spriteship/spriteshipSummer Engine
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 4.5.0
Forks (GitHub): 7
Stars (GitHub): 85
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 2.5.1
Forks (GitHub): 7
Stars (GitHub): 85
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

com.spriteship/spriteship vs Summer Engine
Factcom.spriteship/spriteshipSummer Engine
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub85
Forks (GitHub) (differs)No figure on GitHub7
Last release (differs)Not published2026-10-20
Where it runs (differs)Remote server (spriteship.com/mcp)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle83
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/summerengine/summer
Changes in the last 7 days (differs)06
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Responded 5 days agonot 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

com.spriteship/spriteship

In its own words, on Official MCP Registry:

Build a game's 2D art layer with your agent: characters, animations, tilesets, levels, 5 engines.

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.

How to run each

com.spriteship/spriteship As a remote MCP server

Claude Code
claude mcp add --transport http spriteship https://spriteship.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Summer Engine As a remote MCP server

Claude Code
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 com.spriteship/spriteship 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: com.spriteship/spriteship · What it can do: Summer Engine · 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