pure python Unreal Engine MCP server
Unreal Engine For Claude Desktop MCP server exists for a simple reason — assistants are far more useful when they can act on Unreal Engine For Claude Desktop directly instead of describing what you should do. pure python Unreal Engine MCP server.
This repository contains a Model Context Protocol (MCP) Python server that allows Claude Desktop to interact with Unreal Engine 5.3 (via Remote Control API), creating and manipulating 3D objects based on text prompts. This integration enables Claude to build and modify 3D scenes in Unreal Engine through natural language, representing an early step toward text-to-game-generation technology.
The server ships on PyPI as mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Unreal Engine For Claude Desktop is connected, these are the calls the assistant has available:
list_level_actors — List actors with optional filtering and transform dataget_selected_actors — Inspect the current Unreal Editor selectionselect_actors — Select actors by labelsave_current_level — Save the open mapremote_call — Call any Unreal Remote Control function by object path or actor labelget_object_property — Read any Unreal object propertyset_object_property — Write any Unreal object propertycreate_basic_castle — Build the shared primitive castle workflow directly from MCPverify_basic_castle — Verify the expected castle actor set by prefixreset_basic_castle — Delete castle actors by prefix or strict plan labelsLogging — The server logs detailed information to the console. If you're having issues, check the logs for error messages and tracebacksThis sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Unreal Engine For Claude Desktop's toolset — list_level_actors, get_selected_actors, select_actors and 8 more — is a fair guide to whether it matches your workflow. It is maintained by runeape-sats; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Unreal Engine For Claude Desktop's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_level_actors | List actors with optional filtering and transform data |
| get_selected_actors | Inspect the current Unreal Editor selection |
| select_actors | Select actors by label |
| save_current_level | Save the open map |
| remote_call | Call any Unreal Remote Control function by object path or actor label |
| get_object_property | Read any Unreal object property |
| set_object_property | Write any Unreal object property |
| create_basic_castle | Build the shared primitive castle workflow directly from MCP |
| verify_basic_castle | Verify the expected castle actor set by prefix |
| reset_basic_castle | Delete castle actors by prefix or strict plan labels |
| Logging | The server logs detailed information to the console. If you're having issues, check the logs for error messages and tracebacks. |
{
"mcpServers": {
"unreal-mcp-runeape-sats": {
"command": "uvx",
"args": ["mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.