v1.1.28

v1.1.28

Per-plugin flow group configuration: enable or disable whole groups of a plugin's flows without installing or uninstalling it, with the toggle stored per-user so it never dirties source-tracked config.

Server

• Plugin flow groups. A plugin's flows organize into groups by their name prefix (niagara_*, pcg_*, gas_*), overridable with an explicit group: field on a flow entry. The loader filters a plugin's flows against the user's group toggles before they reach the registry, shrinking the surface to what was opted into.
• ue-mcp plugin config <name>. No arguments opens an interactive menu to pick group states and the save location. Flags make it scriptable: --enable a,b, --disable c,d, --list-groups (shows effective state and which layer set each). Writes ~/.ue-mcp/config.yml by default (user-global, untracked), --local for per-project untracked, --project for the tracked team default. Toggles are opt-out and live under the layered ue-mcp.pluginConfig.<slug>.groups map, merging across the same global / project / env / local cascade as the rest of config.
• ue-mcp init now adds ue-mcp.local.yml to the project .gitignore, keeping per-machine config out of version control.

Bug fixes

• The generated reference config (dist/ue-mcp.default.yml) failed to parse as YAML when a built-in flow step carried an option value containing a colon (the texture_bomb flow description). Scalar and inline-object string option values are now quoted. Runtime defaults are built programmatically and were unaffected, but the shipped reference file (which users copy from to override built-ins) is now valid.

Internals

• New pure module src/plugin/plugin-groups.ts (slug, group derivation, partition) with unit coverage; src/plugin/plugin-config-store.ts handles layered read plus single-layer write. loadPlugins takes the pluginConfig map from project.config.