Today the MCP server ships as a standalone pip package (pip install -e .), separate from the UE plugin. A RunUAT BuildPlugin of UEBridge therefore produces a plugin without the Python that drives it.
Decide the ship path:
- (a) Keep pip as the canonical install and document it clearly as the supported path; or
- (b) Bundle the Python inside the plugin (e.g.
Content/Python or Scripts/ + a Config/FilterPlugin.ini so it survives packaging) for a self-contained artifact.
This gates any Fab-style / packaged distribution and resolves the CanContainContent flag.
Filed as a post-v0.1.0 follow-up (out of v0.1.0 scope). 🤖 Claude Code
Today the MCP server ships as a standalone pip package (
pip install -e .), separate from the UE plugin. ARunUAT BuildPluginofUEBridgetherefore produces a plugin without the Python that drives it.Decide the ship path:
Content/PythonorScripts/+ aConfig/FilterPlugin.iniso it survives packaging) for a self-contained artifact.This gates any Fab-style / packaged distribution and resolves the
CanContainContentflag.Filed as a post-v0.1.0 follow-up (out of v0.1.0 scope). 🤖 Claude Code