Skip to main content
You can connect an AI assistant such as Claude, ChatGPT or Cursor to your Streamloop account. Then you describe what you want (“loop these videos to YouTube every weekday at 9”) and the assistant does the steps for you: uploads, playlists, destinations, schedules and scenes. The assistant connects through Streamloop’s MCP server. MCP (Model Context Protocol) is the standard way AI apps use outside tools. You sign in with your Streamloop account, so there’s no key to copy, and you choose what the assistant may do.
Scenes are in private beta. The scene features below work only on accounts with scene access. See Scenes to request access.

​
Connect your assistant

The server address is https://mcp.streamloop.app/mcp.
  1. In Claude, open Settings → Connectors.
  2. Choose Add custom connector and enter https://mcp.streamloop.app/mcp.
  3. Connect it, sign in to Streamloop, and approve the access.

​
Choose what the assistant may do

When you sign in, you approve one or more permissions: Give it only what it needs. Read-only is enough for questions like “how many credits do I have left?”. The assistant can’t buy credits or spend money: top-ups happen in the dashboard. You can see and revoke connected assistants any time in the Connected Apps panel. See API tokens and connected apps.

​
Workspaces

The assistant works in one workspace at a time, your default one at first. If you’re in several, say which one: “switch to my team’s workspace”. If a loop you know exists doesn’t show up, the assistant is probably in another workspace.

​
The Streamloop skills

The skills are instructions an assistant loads when a task needs them, the same guides Streamloop’s own studio AI assistant uses. They are public at github.com/streamloop/skills. Claude Code gets them with the plugin above; any other agent that reads skills gets them with:
Other assistants get the same tools without the skills. They still work, because the server explains its tools to every assistant.

​
What to ask

Some prompts to start with:
  • “Make a 24/7 lofi loop from these three videos and stream it to my YouTube channel.”
  • “Add a second YouTube destination.” (or “Also send it to Twitch”)
  • “Stream my loop every weekday from 9am to 5pm New York time.”
  • “Why won’t my stream start?”
  • “How many credits do I have, and how long will my loops keep running?”
  • “Build a weather lower third for my scene loop.” (scenes, private beta)
  • “Show the top 5 rows of this Google Sheet as a ticker.” (scenes, private beta)
  • “Put up the guest’s lower third now.” (scenes, private beta)
  • “Cut to the intermission frame with a fade.” (scenes, private beta)

​
What to expect

  • It asks before anything irreversible. Deleting a loop, an upload or a scene, discarding a scene’s draft, or revoking a stream key needs an explicit confirmation. The assistant should tell you what will happen and wait for your yes.
  • It asks before changing what viewers see. Starting a loop puts video in front of the public. Publishing a change to a scene that’s on air needs a confirmation too, because viewers see it at once.
  • Scene edits stay in the draft until you publish. If you have the studio open on the scene, you see the assistant’s edits live. Nothing goes on air until the assistant publishes, and it can do a dry run first that lists what would change.
  • Some steps need you. Connecting a YouTube account needs you to open a Google consent link. For a local file, the assistant may hand you an upload link if it can’t upload the file itself.
  • Some limits still apply. A loop has at most 5 destinations and at most one YouTube channel. You can’t add or remove destinations while a loop is live, but you can turn one off. Multistream is rolling out, so a second destination may not be available on your workspace yet.

​
Next steps

MCP server reference

Endpoint, permissions, errors and how scene editing works.

All MCP tools

Every tool, what it does and the permission it needs.