ue-mcp
Brings Unreal Engine development workflows into Claude conversations, reducing context switching and letting developers query engine APIs, asset pipelines, a…
MCP server that gives AI assistants deep read/write access to the Unreal Editor: 22 category tools covering 612+ actions across blueprints, materials, levels, animation, Niagara VFX, landscape, PCG, GAS, networking, UMG UI, and the build pipeline, plus a YAML flow engine for multi-step workflows. A TypeScript/Node server talks over WebSocket to a C++ bridge plugin that the interactive setup deploys into your Unreal project.
- Generate C++ boilerplate for common UE4/UE5 gameplay mechanics
- Query project structure and asset dependencies programmatically
- Debug blueprint-to-C++ integration issues with code examples
Brings Unreal Engine development workflows into Claude conversations, reducing context switching and letting developers query engine APIs, asset pipelines, and project structure without leaving their IDE or chat interface.
Unreal Engine developers and technical leads who need to rapidly prototype, debug, or document engine-specific code patterns and project configurations.
https://github.com/db-lyon/ue-mcp
By db-lyon
How to Get It
npx ue-mcp init
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Once it’s connected, paste this into Claude:
Help me generate C++ boilerplate for common UE4/UE5 gameplay mechanics
Trust Signals Auto-scanned
Data & Access
Community Pulse Emerging
Discussed on Reddit
- UE_MCP v0.7.10 introduces more idempotency and rollback across every write handl — Reddit · 2 pts
- ue-mcp v0.7.7 is out! — Reddit
- ue-mcp v0.7.18 is out! — Reddit
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 123 GitHub stars; contributors unknown; last commit 1d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 123 GitHub stars; contributors unknown; last commit 1d ago; license no license.