Ext Ops Panel
Open dashboard
Comparison

Gessa: game asset generation for AI agents vs Summer Engine

Gessa: game asset generation for AI agents is an MCP server published by gessa.ai. 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: 3 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers)). As of our marketplace pass on 2026-11-05. 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
MarketplaceGessa: game asset generation for AI agentsSummer Engine
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 132
Downloads/week (npm): 24
Not marked · First seen
Listed
Version: 4.5.0
Downloads/month (npm): 15 365
Downloads/week (npm): 4 559
Forks (GitHub): 9
Stars (GitHub): 91
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 2.5.1
Forks (GitHub): 9
Stars (GitHub): 91
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 4.9.1
Downloads/month (npm): 15 365
Downloads/week (npm): 4 559
Forks (GitHub): 9
Stars (GitHub): 91
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

Gessa: game asset generation for AI agents vs Summer Engine
FactGessa: game asset generation for AI agentsSummer Engine
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub91
Forks (GitHub) (differs)No figure on GitHub9
Last release (differs)Not published2026-10-28
Where it runs (differs)Remote server (api.gessa.ai/mcp/rpc)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not 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 days00
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Status out of date: last check 4 days ago returned HTTP 405Responded 1 h ago

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

Gessa: game asset generation for AI agents

In its own words, on Official MCP Registry:

Generate game-ready 3D models, textures, and audio from natural language, over MCP.

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

Gessa: game asset generation for AI agents As a remote MCP server

Claude Code
claude mcp add --transport http gessa-game-asset-generation-for-ai-agent https://api.gessa.ai/mcp/rpc --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: GESSA_API_KEY (secret), 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.

Both endpoints responded at the last daily 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

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

What it can do: Gessa: game asset generation for AI agents · 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. Package data comes from the public npm registry (registry.npmjs.org). 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