Upstream.so — Claude Code MCP server for live streams
A remote MCP server for the Upstream.so cloud streaming platform. It lets an assistant start broadcasts, edit playback queues and plan schedules.
claude mcp add --transport http upstream https://studio.upstream.so/mcpWhat Upstream.so does
One URL, https://studio.upstream.so/mcp, over Streamable HTTP. There is no local process and no package to pull down. Every tool follows the public Upstream API, so ownership checks, validation and rate limits match the REST endpoint behind it.
Streams come first: list them with pagination, fetch one by UUID, create, patch, delete, start and stop. Stopping cuts a live broadcast for viewers, so keep approval prompts on. Scheduling is not a separate tool — create_stream and update_stream accept a schedule object with start and end times, repeats, and a continuous mode that carries its own work and rest intervals. Playback queues, media library search and multistream destinations round out the set.
OAuth is the recommended path: add the URL, sign in on studio.upstream.so, approve the access. Your client gets a token, not your password. Clients that send custom headers can use a Personal Access Token from Profile → API Keys as Authorization: Bearer. Both grant the same tools, including ones that change or delete data — the mcp:use scope is not read-only. A saved API-key header can stop a client from starting OAuth, so clear it before reconnecting.
What it helps with
- start a broadcast on YouTube or Twitch from the chat
- reorder items in a playback queue
- find a file in the media library
- set up a repeating schedule with breaks
- add a destination for multistreaming
Example prompts for the agent
- List my streams, newest first
- Start the stream on my Twitch channel
- Move this clip to the top of the playback queue
How to install Upstream.so
Platform CLI: remote server
claude mcp add --transport http upstream https://studio.upstream.so/mcpPlatform CLI: remote server
codex mcp add upstreamso --url https://studio.upstream.so/mcpConfig file
{
"mcpServers": {
"upstreamso": {
"url": "https://studio.upstream.so/mcp"
}
}
}Config file
{
"servers": {
"upstreamso": {
"type": "http",
"url": "https://studio.upstream.so/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http upstreamso https://studio.upstream.so/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Upstream.so
How do I install Upstream.so in Claude Code?
Run claude mcp add --transport http upstream https://studio.upstream.so/mcp, then open Claude, run /mcp and pick Upstream to sign in and approve access.
What does Upstream.so do?
It is a remote MCP server for the Upstream.so platform. An assistant uses it to manage streams, playback queues, schedules and multistream destinations.
Do I need an API key?
Not if your client supports OAuth — you sign in on studio.upstream.so. Clients with custom headers can send a Personal Access Token as Authorization: Bearer.
