Skip to main content
Streamloop runs a hosted Model Context Protocol (MCP) server so AI agents can manage streams as tools — uploading media, building playlists, connecting destinations, and starting, scheduling, and monitoring 24/7 streams. It’s a thin, OAuth-protected layer over the same API as everything else, so an agent can do what you can do in the dashboard.

​
Endpoint

URLhttps://mcp.streamloop.app/mcp
TransportStreamable HTTP
AuthOAuth 2.1 (PKCE, S256)

​
Connect an agent

Add the server URL to any MCP-capable client. On first use the client opens Streamloop’s OAuth flow; you sign in and approve the scopes, and the agent gets a token — no API key to copy or paste.
In Claude (Settings → Connectors / “Add custom connector”), add an MCP server with the URL https://mcp.streamloop.app/mcp, then complete the sign-in prompt.

​
Permissions

The agent only gets the scopes you approve during sign-in. Grant the least it needs:
ScopeLets the agent
streamloop:readRead streams, destinations, playlists, and billing status
streamloop:writeCreate and control streams, destinations, and playlists
streamloop:destructiveDelete streams and destinations
streamloop:billingRead billing and usage, and create top-up links

​
Built-in safety

  • Destructive and financial tools are marked. Tools that delete resources or spend money carry a destructiveHint and require explicit confirmation (confirm: true) before they run, so an agent can’t quietly delete a stream or create a top-up by accident.
  • Scope-gated. Each tool requires a specific scope; a tool the token isn’t scoped for isn’t callable.
The MCP tools mirror the REST API one-to-one — same operations, same data. See the full list on the Tools page.