Skip to main content
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.
You ask in plain language. The assistant picks the tools. diagnose_session is the one to know. Give it a session id and it reconstructs what happened from the platform’s records, the viewer’s telemetry, the disconnect code and the Unreal log. It then says what went wrong, whose side it is on and what to do.

Example questions

  • “Give me yesterday’s health report for Showroom and diagnose the worst three sessions.”
  • “Session session_1790294409382_3035 failed for a customer. What happened and what do I tell them?”
  • “My build has been distributing for an hour. Is it stuck?”
  • “How many viewers queued this week and how long did they wait?”
  • “Which browsers do my viewers use?”
  • “When is my next billing date?”
  • “How do I put a new build of my Unreal project live from my computer?”

Putting a build live

The MCP server runs in Streampixel’s cloud, so it cannot package a project or upload a build from your computer. Ask the assistant “How do I put my Unreal project live?”. It calls deploy_from_my_computer and gives you the Streampixel command line steps for your project. You can also 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. Working with Unreal MCP shows how the tools work together.

Limits

  • Each question covers at most 31 days.
  • Each account has a budget of tool calls per minute and per day, and of log scans per hour, so a runaway conversation cannot overload the analytics store. The assistant is told when to wait.
  • Invoices and payment history are not available through the assistant. They are on the dashboard’s Billing page.