Comparison

VeyraX vs io.github.ChiR24/unreal-engine-mcp

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). 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
Marketplace	VeyraX	io.github.ChiR24/unreal-engine-mcp
Docker MCP Catalog	Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 492 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen 2026-10-11	Listed Version: sha256:bbc6bede740a Forks (GitHub): 183 Pulls (Docker Hub): 39 331 Stars (Docker Hub): 4 Stars (GitHub): 964 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 0.6.0-beta-f Downloads/month (npm): 3 146 Downloads/week (npm): 697 Forks (GitHub): 183 Stars (GitHub): 964 Not marked · First seen 2026-10-11

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

VeyraX vs io.github.ChiR24/unreal-engine-mcp
Fact	VeyraX	io.github.ChiR24/unreal-engine-mcp
Marketplaces that list it (differs)	1 (worse)	2 (better)
Stars (GitHub) (differs)	48 (worse)	964 (better)
Pulls (Docker Hub) (differs)	18 492 (worse)	39 331 (better)
Forks (GitHub) (differs)	19 (worse)	183 (better)
Last release (differs)	Not published	2026-10-16
Where it runs (differs)	On your machine (mcp/veyrax)	Remote server or your machine
Transport (differs)	stdio	stdio, Streamable HTTP
Tools it declares (differs)	3	23
Environment variables it asks for (differs)	1, secrets among them: 1	11, secrets among them: 1
Licence (differs)	Not stated	MIT
Repository (differs)	github.com/veyrax/veyrax-mcp	github.com/chir24/unreal_mcp
Changes in the last 7 days (differs)	0	2
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Answered with HTTP 404 (5 days 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

VeyraX

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

io.github.ChiR24/unreal-engine-mcp

In its own words, on Official MCP Registry:

EngineWire: drive the Unreal Editor (UE 5.0-5.8): levels, Blueprints, UI, materials, VFX and more.

How to run each

VeyraX As a local MCP server: Docker image

Claude Code

claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyrax

Requires: VEYRAX_API_KEY (secret)

io.github.ChiR24/unreal-engine-mcp As a local MCP server: npm package

Claude Code

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-server

Requires: MCP_AUTOMATION_CAPABILITY_TOKEN (secret), UE_PROJECT_PATH

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

Only VeyraX declares

get_flow
get_tools
tool_call

Only io.github.ChiR24/unreal-engine-mcp declares

animation_physics
build_environment
control_actor
control_editor
inspect
manage_ai
manage_asset
manage_audio
manage_blueprint
manage_character
manage_combat
manage_effect

Show the remaining 11

manage_gas
manage_geometry
manage_interaction
manage_inventory
manage_level
manage_level_structure
manage_networking
manage_pcg
manage_sequence
manage_tools
system_control

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only VeyraX asks for

VEYRAX_API_KEY (secret)

Only io.github.ChiR24/unreal-engine-mcp asks for

LOG_LEVEL
MCP_ADDITIONAL_PATH_PREFIXES
MCP_AUTOMATION_ALLOW_NON_LOOPBACK
MCP_AUTOMATION_CAPABILITY_TOKEN (secret)
MCP_AUTOMATION_HOST
MCP_AUTOMATION_MAX_MESSAGES_PER_MINUTE
MCP_AUTOMATION_PORT
MCP_AUTOMATION_USE_TLS
MCP_CONNECTION_TIMEOUT_MS
MCP_REQUEST_TIMEOUT_MS
UE_HOST
UE_PROJECT_PATH

Show the remaining 2

UE_RC_HTTP_PORT
UE_RC_WS_PORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: VeyraX · What it can do: io.github.ChiR24/unreal-engine-mcp · 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. Figures come from our own regular passes over the marketplaces, last read on 2026-10-21. We publish no contact details for plugin publishers.