Unreal Engine Skills for Claude Code Plugin Guide
Guide to Epic Games' Claude Code skill/plugin pack for Unreal Engine MCP workflows, editor setup, hooks, platform support, and safe agent use.
Key takeaways#
Unreal Engine Skills for Claude Code is an Epic Games plugin pack for Claude Code users working in Unreal Engine projects. It packages a Claude Code skill named unreal-mcp plus a session-start hook that nudges Claude toward Unreal Engine conventions. The workflow depends on Unreal Editor's ModelContextProtocol plugin and the AllToolsets plugin, which expose hundreds of editor tools across actors, blueprints, materials, Niagara, Control Rigs, Sequencer, State Trees, widgets, Gameplay Ability System, automation testing, and related toolsets.
What it is#
The repository is best understood as a resource pack for Unreal developers using Claude Code, not as a standalone SaaS tool. Its README explains that the unreal-mcp skill gives Claude instructions and workflows for driving Unreal Editor through MCP. The included hook identifies the repository as an Unreal Engine project when a Claude Code session starts, resumes, or clears, so Claude defaults to Unreal-specific conventions such as C++, UObject, Slate, and UHT.
That matters because Unreal automation is highly contextual. An agent that writes generic C++ or blindly edits assets can break projects quickly. This resource gives Claude a project-level nudge and a documented path to use Unreal's MCP server instead of guessing where editor state lives.
Setup outline#
Before installing the plugin, enable Unreal Editor's ModelContextProtocol plugin and AllToolsets plugin. The README notes that AllToolsets provides the actual tools; without it, the MCP server exposes none. Start the MCP server from the editor with ModelContextProtocol.StartServer, or configure autostart with the setup reference in the skill directory. Claude Code users can install the plugin from Anthropic's official Claude Code plugin marketplace with /plugin install unreal-engine-skills-for-claude-code@claude-plugins-official. Teams can commit an enabled plugin setting to .claude/settings.json so trusted project folders prompt developers to install it.
Platform notes#
The hook is a bash script. macOS and Linux work with normal shell environments. Windows users need Git Bash or WSL for the session-start hook; native PowerShell alone does not provide bash on PATH. The README says the plugin's MCP tools can still work without the hook, but the automatic project-context note will not run.
Security and review checklist#
Treat Unreal MCP access as powerful editor automation. Verify the project folder is trusted before enabling team-level plugin settings. Review generated asset changes, blueprint edits, automation-test actions, and file modifications before committing. If the editor is stopped, consider the optional proxy mentioned in the repository to keep the client connection stable, but do not assume it removes the need for review.
Best fit#
This resource is strongest for Unreal teams that already use Claude Code and want editor-aware assistance. It can help with navigation, asset inspection, automation workflows, and project-specific Unreal conventions. It is less useful for teams that do not use Claude Code or have not enabled Unreal's MCP toolsets. In those cases, the repository is still a helpful reference for how Epic expects Claude Code skills and MCP-driven Unreal workflows to be structured.