unreal-lazy-mcp
Related Servers
Alternatives to unreal-lazy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to operate the Unreal Editor via MCP: reading, creating, and editing blueprints at the node level, authoring materials and UMG widgets, auditing projects, and verifying runtime behavior in PIE with read-back checks.341Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to search, describe, execute, and configure capabilities in a running Unreal Editor through its local MCP endpoint, forwarding calls and returning the editor’s own results or connection errors.72 npmMIT
- AlicenseBqualityBmaintenanceEnables Unreal Engine editor development through typed Jev decisions and guarded MCP tools, including tool recommendation, diagnostic classification, scene inspection, and preview/apply blockout operations with undo.54MIT
- AlicenseNot gradedqualityCmaintenanceDrives Unreal Engine 5 from any AI assistant by exposing the open editor as MCP tools over Unreal's built-in Remote Control API, so users can spawn, list, move, and delete actors, search assets, and read or write properties through natural language. No custom plugin or in-engine code is required, and it includes a raw function-call tool plus batch execution for arbitrary BlueprintCallable functions.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to inspect and work with Unreal Engine projects by parsing C++ symbols, Blueprints, and .uasset data over MCP, supporting tasks like symbol tracing, asset search, and code generation.-
- AlicenseBqualityDmaintenanceEnables AI coding agents to control and interact with Unreal Engine 4.27 editor through MCP protocol, translating tool calls into HTTP commands for the in-editor plugin.100MIT
TDQS
Scored across 4 tools
The four tools occupy distinct roles: discovery (find_tools), browsing (list_toolsets), schema inspection (get_tool_details), and execution (invoke). The only overlap is between find_tools and list_toolsets, but the descriptions explicitly steer users toward find_tools, keeping boundaries clear.
Three of four tools follow a clean verb_noun pattern (get_tool_details, list_toolsets, find_tools). The bare verb 'invoke' is a minor but understandable deviation for the terminal execution step.
Four tools is a lean but well-scoped gateway pattern where each tool earns its place (discover, browse, inspect, execute). It is slightly on the minimal side but not thin given the proxy role.
The surface covers the full discovery-to-execution lifecycle for a proxied toolset, including schema inspection before invocation. Minor gaps exist (no bulk tool listing within a toolset, no batch invoke), but agents can work around them via find_tools and repeated invoke calls.