ClaudeSuperPower
SubmitLog in

unreal-engine-skills-for-claude-code

Plugin

Control Unreal Editor directly from Claude Code via MCP. Hundreds of tools exposed via Unreal's ToolsetRegistry across 30+ toolsets: actors, blueprints, materials, Niagara, Control Rigs, Sequencer, State Trees, widgets, Gameplay Ability System, automation testing, and more.

160Testing

Install

claude plugin install unreal-engine-skills-for-claude-code@claude-plugins-official

What is unreal-engine-skills-for-claude-code?

Control Unreal Editor directly from Claude Code via MCP. Hundreds of tools exposed via Unreal's ToolsetRegistry across 30+ toolsets: actors, blueprints, materials, Niagara, Control Rigs, Sequencer, State Trees, widgets, Gameplay Ability System, automation testing, and more.

What's inside

4 bundled components — installing the plugin installs all of them.

Skills (3)

create-toolset

Use this skill when authoring or extending an Unreal Engine toolset, a class of static, AI-callable functions registered with `ToolsetRegistry` and exposed through the unreal-mcp server. Trigger when the user wants to add, expose, or register a new tool method, create a new toolset, or extend an exi

unreal-mcp

Use this skill to perform actions inside an Unreal Engine project via a live-editor MCP connection. Trigger when the user wants to change, query, or run something in their Unreal Engine project, not for conceptual or docs questions. Concrete triggers: spawn/move/duplicate/transform actors in a level

unreal-skill

Use this skill when creating, editing, or reviewing an Unreal Engine Agent Skill, a named bundle of instructions registered with the unreal-mcp server (distinct from Claude Code's harness skills under `.claude/skills/`). Trigger when the user wants to add or change a skill that the in-editor agent w

What this can do

Capabilities declared by the plugin's own components — read straight from their frontmatter, not inferred.

Inherit all session tools

3 components declare no tool restrictions

~778 tokens of context used while enabled, before you invoke anything

Trust

87/100 · Excellent

2 factors scored below maximum

Unscoped tools

Documentation

README · ~5 min read

Unreal Engine Skills for Claude Code

Control Unreal Editor directly from Claude Code via MCP. Hundreds of tools exposed via Unreal's ToolsetRegistry across 30+ toolsets: actors, blueprints, materials, Niagara, Control Rigs, Sequencer, State Trees, widgets, Gameplay Ability System, automation testing, and more.

Contents

Skills

  • unreal-mcp (skills/unreal-mcp) - instructions and workflows for driving the Unreal Editor via MCP.

Hooks

  • SessionStart (hooks/unreal-context.sh) - injects a short note identifying the repo as an Unreal Engine project so Claude defaults to UE conventions (C++/UObject, Slate, UHT) and prefers the unreal-mcp skill. Runs on startup, resume, and clear.

Prerequisites

  1. Unreal Editor with the ModelContextProtocol and AllToolsets plugins enabled (AllToolsets provides the tools; the server exposes none without it)
  2. Editor running with the MCP server started - run ModelContextProtocol.StartServer in the console, or enable bAutoStartServer per skills/unreal-mcp/references/setup.md

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just plugins.

Subagents

All subagents →

agent-creator

Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: <example> Context: User wants to create a code review a

32.8K stars

agent-sdk-verifier-ts

Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.

32.8K stars

pr-test-analyzer

Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-creat

32.8K stars