Related Servers

Domain-prefixed families (ue_bp_, ue_umg_, ue_pcg_, ue_foliage_, ue_sequence_) make each tool's target resource obvious, and descriptions explicitly disambiguate near-neighbors like ue_set_replication vs ue_set_component_replication vs ue_set_net_config. A few pairs could still be confused on first pass — ue_import_assets already accepts .wav yet ue_import_audio duplicates it, ue_status vs ue_editor_status both report editor state, and ue_editor_open vs ue_open_level both use "open" for different targets — but these are rare exceptions across 163 tools.

The dominant ue_<domain>_<verb>_<noun> pattern with coherent families (ue_create_*, ue_*_info, ue_*_list, ue_*_status, ue_bp_add_*, ue_bt_add_*) is highly predictable and makes tool discovery feasible at this scale. Minor deviations exist — ue_make_folder breaks the create_* convention, the preset_* family uses a different prefix, and tools like ue_read_log, ue_reflect_enum, and ue_live_compile don't fit the standard verb set — but they are rare and internally readable.

163 tools is more than six times the 25+ threshold and will overwhelm an agent's selection space even with good naming, so the set is too large for practical use in a single MCP server. The scope is genuinely broad (project management, C++ build, Blueprint graphs, UMG, AI, GAS, PCG, foliage, landscape, sequencer, networking, asset acquisition), which prevents a score of 1, but the count reflects roughly fifteen sub-domains packed into one surface and includes partial duplicates like ue_import_audio and ue_spawn_many.

Coverage is exceptional: nearly every sub-domain has create + inspect + modify operations, and Blueprint graph editing, PCG, foliage, AI, and sequencer are unusually deep, with no obvious dead ends in the core asset/actor/project workflows. The remaining gaps are documented engine-level limits with workarounds — Niagara emitter stacks, EQS query internals, UMG root widgets, and AnimGraphs cannot be scripted, landscape creation requires the editor, and there is no undo tool — so agents can route around them via ue_exec_python, ue_cpp_class_create, or manual editor steps.