What problem does it solve? Adding a new command to the UE Audio MCP plugin requires touching six files across C++ headers, implementations, build configuration, command registration, Python tool wrappers, and tests, and missing any one of them breaks the build or leaves the command unreachable. ## Core Features & Use Cases - Six-File Checklist: Walks through declaring the command class in the correct group header, implementing Execute() with JSON param validation, updating Build.cs dependencies, registering in UEAudioMCPModule.cpp, writing the Python MCP tool wrapper, and adding pytest coverage. - UE 5.7 Gotchas & Security Rules: Documents engine-specific pitfalls (UE_LOG format validation, SpawnActor FTransform overloads, GEditor null checks) and enforces path validation (/Game/ prefix, no traversal) plus localhost-only TCP constraints. - Use Case: You want to expose a new MetaSounds operation to MCP clients. Follow the checklist to add the C++ command, register it in the dispatcher, wrap it as a Python tool with shared _ok/_error helpers, and verify with pytest and the plugin build script. ## Quick Start Add a new command named set_reverb_send that routes a MetaSounds output to a Wwise reverb bus, following the six-file checklist.
