MCP Unreal Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute-pythonC | 在Unreal中执行Python代码 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose of executing Python code within Unreal.
With only one tool, naming consistency is inherently perfect. The tool name 'execute-python' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
A single tool is too few for a server named 'MCP Unreal Server', which suggests a broader scope related to Unreal Engine. This minimal toolset feels thin and inadequate for typical Unreal automation or interaction tasks.
The tool surface is severely incomplete for an Unreal server. It only provides Python execution, lacking essential operations like asset management, level editing, blueprint interaction, or any other common Unreal Engine workflows, leaving significant gaps.