io.github.ChiR24/unreal-engine-mcp vs DeadCat: Reaper
io.github.ChiR24/unreal-engine-mcp is an MCP server published by ChiR24. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). DeadCat: Reaper is an MCP server published by systemblueio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |   io.github.ChiR24/unreal-engine-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.1-beta-a Downloads/month (npm): 2 910 Downloads/week (npm): 750 Forks (GitHub): 185 Stars (GitHub): 1 021 Not marked · First seen |
Listed Version: 0.1.5 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:bbc6bede740a Forks (GitHub): 185 Pulls (Docker Hub): 40 079 Stars (Docker Hub): 4 Stars (GitHub): 1 021 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
| Fact | io.github.ChiR24/unreal-engine-mcp | DeadCat: Reaper |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 021 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 40 079 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 185 | No figure on GitHub |
| Last release (differs) | 2026-11-06 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (https://github.com/systemblueio/DeadCat/releases/download/v0.1.5/deadcat-reaper.mcpb) |
| Transport (differs) | stdio, Streamable HTTP | stdio |
| Tools it declares (differs) | 23 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/chir24/unreal_mcp | github.com/systemblueio/deadcat |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 47 h ago returned HTTP 404 | no remote endpoint we check |
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
io.github.ChiR24/unreal-engine-mcp
EngineWire: drive the Unreal Editor (UE 5.0-5.8): levels, Blueprints, UI, materials, VFX and more.
DeadCat: Reaper
Operate a REAPER session in plain language, with writes verified against REAPER feedback.
How to run each
io.github.ChiR24/unreal-engine-mcp As a local MCP server: npm package
claude mcp add --env "MCP_AUTOMATION_CAPABILITY_TOKEN=<YOUR_MCP_AUTOMATION_CAPABILITY_TOKEN>" --env "UE_PROJECT_PATH=<YOUR_UE_PROJECT_PATH>" --transport stdio unreal-engine-mcp -- npx -y unreal-engine-mcp-serverRequires: MCP_AUTOMATION_CAPABILITY_TOKEN (secret), UE_PROJECT_PATH
DeadCat: Reaper
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.ChiR24/unreal-engine-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of DeadCat: Reaper publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of DeadCat: Reaper publish no settings it asks for, so we do not compare settings.
What it can do: io.github.ChiR24/unreal-engine-mcp · What it can do: DeadCat: Reaper · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.