Beta. The Streampixel command line (version 0.1.0-beta.1) and the Streampixel MCP server are in beta. Commands, tools and their output can still change before the stable release.
The loop
1
Edit the project
The agent changes assets, Blueprints, levels or settings through Unreal MCP. Without Unreal MCP, it edits the project files.
2
Check and package
streampixel doctor checks the project is ready to stream. streampixel package packages a Windows build. When either reports a problem, with a file and line or an asset, the agent fixes it through Unreal MCP and runs the same step again.3
Upload, deploy and test
streampixel upload, then streampixel deploy, then streampixel test. The test starts one short session and reports whether a picture arrived. It also prints the session id.4
Diagnose
The agent passes that session id to
diagnose_session on the Streampixel MCP. It reads the session’s records and the application’s own log, and says what went wrong and what to do. For a build that stays in processing, it uses get_build_status with the build id.Who does what
- In this loop the agent packages, uploads and deploys with the command line, because the Streampixel MCP runs in the cloud and cannot reach the files on your computer. Outside it, you can still upload it in the dashboard, let cloud builds package it from your repository, or give the REST API’s Upload File endpoint a download link to a zip you host.
- The Streampixel MCP can tell an assistant the command line steps for a project. Ask “How do I put my Unreal project live?” and it uses
deploy_from_my_computer. - Unreal MCP is set up in the Unreal Editor. See Epic’s documentation for it.
Set it up
- Install the command line and sign in.
- Connect your agent to the Streampixel MCP.
- Run
streampixel initin your Unreal project folder, so the agent knows these steps.