No user-submitted related servers found.
Scored across 54 tools
Many tools are explicitly scoped and the descriptions are unusually detailed, but there are several close clusters that could trip up an agent: generic unreal_preview/unreal_apply vs. unreal_workflow_preview/unreal_workflow_apply and the many specific *_preview variants; unreal_verify/unreal_validate/unreal_workflow_inspect; and jev_route/jev_catalog_rerank/jev_decide. Descriptions help, but the sheer number of overlapping action words makes misselection likely without careful reading.
The server mostly uses readable snake_case with domain prefixes, and lifecycle verbs like start/job/cancel are consistent within validation, functional, and performance groups. However, the pattern is not uniform: generic unreal_preview/unreal_apply coexist with unreal_workflow_preview/unreal_workflow_apply, plural/singular pairs like unreal_actors/unreal_actor_details and unreal_assets/unreal_asset_details are confusing, and the jev_* tools mix catalog verbs with abstract verbs like decide, route, and triage.
With 54 tools, this is an extreme count for a single MCP server regardless of the broad Unreal Editor scope. Even though the tools are grouped into coherent domains, the aggregate surface will significantly burden context windows and make reliable tool selection harder. This places it in the 50+ extreme-mismatch range.
For a safety-oriented preview/apply/review adapter, the coverage is strong: asset inspection, workflow preview/apply/receipt, validation, functional testing, Blueprint compilation, and performance capture all have lifecycle tools. Minor gaps exist, such as no explicit workflow enumeration, no snapshot cleanup, no save operation, and very limited Blueprint editing, but these are either intentional by design or workable around.