← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionUnreal Engine MCP ServerAutomate Unreal Engine 5 with AI.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS53 / 100 · D79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Teams developing games, levels, animation, or visual effects with Unreal Engine 5.
  • Users who want AI to perform repetitive editor and content-production tasks.
  • Users comfortable managing Unreal projects, plugins, and local development environments.
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Projects that do not use Unreal Engine.
  • Blueprint-only environments that cannot install a pre-built plugin or compile a code plugin.
  • Public or remote exposure without appropriate network security configuration.
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Access to and control of the specified Unreal project.
  • Installation and execution of the MCP Automation Bridge plugin and required Unreal plugins.
  • Some features require Python, Editor Scripting Utilities, Niagara, Gameplay Abilities, Smart Objects, or other plugins.
  • Node.js 18 or later is required for the TypeScript Bridge.
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • The server can modify assets, actors, levels, project settings, and other game-development content.
  • Enabling non-loopback addresses exposes the automation bridge to the local network; use trusted networks and enable capability-token authentication.
  • Incorrect console commands, scripts, or automation actions can change project content or editor state.
  • Pre-built plugin binaries are tied to specific Unreal Engine versions.
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Cursor, Claude CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools230