No user-submitted related servers found.
Scored across 23 tools
Every tool has a distinct purpose: lifecycle (build, compile, connect, delete), read (nodes, connections, topology), PIE runtime operations, and diagnostics/health. Overlaps like ue5_read_blueprint vs. ue5_read_nodes are clearly scoped (whole asset vs. specific graph), and ue5_run_batch vs. ue5_execute_command are clearly differentiated (whitelisted sequences vs. escape hatch).
Naming is highly consistent with a verb_noun pattern (e.g., ue5_list_assets, ue5_read_blueprint, ue5_delete_asset), and all tools share the ue5_ prefix. Minor deviation: ue5_run_batch and ue5_execute_command are more generic verbs ('run' vs. 'execute') but still readable and not chaotic.
At 23 tools, the surface is on the heavy side but still scoped to the domain (Blueprints, assets, PIE, diagnostics, audio/video). A few tools like ue5_build_batch or ue5_disconnect_pin are edge-case, and ue5_execute_command duplicates many others as an escape hatch, making the count feel slightly inflated. Still, each tool has a defensible role.
The toolset covers the full Blueprint lifecycle: create (build, batch), read (list, read_blueprint, read_nodes, read_connections), modify (connect, disconnect, delete_node, save), and verify (compile, PIE start/stop/read, logs, diagnostics). It also covers delete_asset and runtime property access. Missing operations are minimal and covered by the escape hatch (ue5_execute_command).