Skip to main content
Glama
Flux-Point-Studios

Unreal Engine MCP Server

system_control

Destructive

Run profiling, set quality and CVars, execute console commands, run Unreal Build Tool, manage widgets, and execute scripts in Unreal Engine.

Instructions

Run profiling, set quality/CVars, execute console commands, run UBT, manage widgets, and execute scripts (Python, console batch, editor utility).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
levelNo
valueNo
actionYesAction
filterNo
targetNo
commandNo
dry_runNoIf true, validate the script without executing it (for execute_script action).
enabledNoWhether the item/feature is enabled.
sectionNo
categoryNo
channelsNo
platformNo
argumentsNo
childClassNo
configNameNo
parentNameNo
resolutionNoResolution setting (e.g., 1024x1024).
widgetPathNoWidget blueprint path.
profileTypeNo
script_nameNoOptional friendly name for the script (for logging/history).
script_typeNoType of script to execute (for execute_script action). python: Execute Python script via editor Python plugin. console_batch: Execute multiple console commands separated by newlines. editor_utility: Run an Editor Utility Blueprint/Widget by asset path.
configurationNo
script_contentNoThe script code to execute, or asset path for editor_utility type (for execute_script action).
timeout_secondsNoExecution timeout in seconds (default: 30, max: 300).
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructive behavior (destructiveHint=true, readOnlyHint=false), but the description adds no further behavioral context. It does not disclose potential side effects (e.g., executing arbitrary scripts, changing project settings, affecting the editor state) or any safety considerations. It merely restates action categories.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently enumerates six function areas. It is concise and front-loaded with the main actions, avoiding unnecessary detail. However, it is a simple list rather than structured guidance, so it gets a 4 rather than 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 25 parameters, multiple action types, and no output schema, this description is far from complete. It does not clarify how to construct a valid request, which parameters apply to which actions, or what to expect in response. The broad list of capabilities is insufficient for correct invocation, especially for niche actions like 'spawn_category' or 'lumen_update_scene'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schemas coverage is low (36%), so the description must compensate. It only hints at script types (Python, console batch, editor utility) and CVars, but does not explain key parameters like 'key', 'level', 'value', 'filter', or how they relate to specific actions. The description adds minimal semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly lists a range of actions (profiling, quality/CVars, console commands, UBT, widgets, scripts), which clearly indicates what the tool can do. However, it does not differentiate from sibling tools like manage_performance or manage_widget_authoring, which may overlap, so it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or fallback tools. The description simply lists capabilities without context on selection, so it offers no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flux-Point-Studios/unreal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server