UE5 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | |
| INJECT_CONTEXT | No | Auto-inject UE5 context on tool responses | false |
| UNREAL_MCP_URL | No | Unreal plugin HTTP server URL | http://localhost:3000 |
| MCP_REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds | 30000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unreal_statusA | Check if Unreal Editor is running with the plugin. Currently: NOT CONNECTED. Please start Unreal Editor with the plugin enabled. |
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
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is perfect; 'unreal_status' is a clear, self-consistent name.
A single tool for a server named 'UE5 MCP Server' is too few; the server's apparent scope demands more operations (e.g., asset manipulation, editor commands).
The server only provides a status check, missing all interactive capabilities expected from a UE5 integration, making it severely incomplete.