Ext Ops Panel
Open dashboard
Comparison

EverArt (Archived) vs Summer Engine

EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-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
MarketplaceEverArt (Archived)Summer Engine
Docker MCP Catalog Listed
Version: sha256:98c2aa1b6231
Forks (GitHub): 11 788
Pulls (Docker Hub): 18 807
Stars (Docker Hub): 3
Stars (GitHub): 91 289
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.3.0
No figure published
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 2.5.1
Forks (GitHub): 6
Stars (GitHub): 76
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

EverArt (Archived) vs Summer Engine
FactEverArt (Archived)Summer Engine
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 289 (better)76 (worse)
Pulls (Docker Hub) (differs)18 807No figure on Docker Hub
Forks (GitHub) (differs)11 788 (better)6 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp/everart)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle83
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/summerengine/summer
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-12
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

EverArt (Archived)

In its own words, on Docker MCP Catalog:

Image generation server using EverArt's API.

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

EverArt (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "EVERART_API_KEY=<YOUR_EVERART_API_KEY>" --transport stdio everart -- docker run -i --rm -e EVERART_API_KEY mcp/everart

Requires: EVERART_API_KEY (secret)

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.

Tools each declares

The marketplaces of Summer Engine publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Summer Engine publish no settings it asks for, so we do not compare settings.

What it can do: EverArt (Archived) · What it can do: Summer Engine · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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