uemcp vs Summer Engine
uemcp is an MCP server published by ATDev-Inc. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Summer Engine is an MCP server published by SummerEngine. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-08. 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
| Marketplace |  uemcp |   Summer Engine |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.1.0 Downloads/month (PyPI): 524 Downloads/week (PyPI): 615 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.5.0 Downloads/month (npm): 15 365 Downloads/week (npm): 4 559 Forks (GitHub): 9 Stars (GitHub): 95 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 2.5.1 Forks (GitHub): 9 Stars (GitHub): 95 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): 95 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 | uemcp | Summer Engine |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 4 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 95 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 9 (better) |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | On your machine (uemcp) | Remote server or your machine |
| Transport (differs) | Not stated | 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) | Not a bundle | 129 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/atdev-inc/uemcp | github.com/summerengine/summer |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-13 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 20 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
uemcp
Open source MCP server that lets Claude drive Unreal Engine 5 with no plugin to compile
Summer Engine
The game engine built for AI. Any agent makes a multiplayer game and publishes it.
How to run each
uemcp
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/mcpCommands 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: uemcp · What it can do: Summer Engine · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.