Upstream.so MCP server

Upstream.so — MCP Server

The official Model Context Protocol server for [Upstream.so][home], the cloud live-streaming platform. Point an AI assistant at one URL and it can run your channels: start and stop streams, reorder playback queues, search your media library, plan schedules, and manage multistream destinations.

It is a remote server — nothing to install, no npm package, no local process. It mirrors the public [Upstream API][api] one-to-one, so every tool runs the same validation, ownership rules and rate limits as the REST endpoint behind it.

┌───────────────┐   MCP (Streamable HTTP)   ┌────────────────────┐
  │  your AI       │ ────────────────────────► │ studio.upstream.so │
  │  (Claude, ...) │ ◄──── tool results ────── │        /mcp        │
  └───────────────┘                            └─────────┬──────────┘
                                                         │ same code path
                                                         ▼
                                              ┌────────────────────┐
                                              │  Upstream API v1    │
                                              └────────────────────┘

Endpoint

Authentication

Connect with OAuth when your client supports it. Add the server URL, sign in directly on studio.upstream.so, and review the requested access. Your AI client receives an access token, never your Upstream password. Remove its access under Profile → Connected apps.

For clients with custom request headers, a Personal Access Token remains available under Profile → API Keys. Create a dedicated key for each client and store it in the client's secret settings. Existing API-key connections keep working.

Both methods grant access to the supported MCP tools for your account, including actions that change or delete data. OAuth's mcp:use scope is not a read-only mode. Enable your client's approval prompts and begin with a read-only request.

The legacy X-Upstream-Api-Key header still works. New API-key connections should send Authorization: Bearer.

Connecting

ChatGPT

1. Enable Developer mode under Settings → Security and login, if your account and workspace allow it.
2. Open Plugins, select the plus button, and name the connection Upstream.
3. Enter https://studio.upstream.so/mcp. Choose OAuth authentication when prompted.
4. Sign in on Upstream, review the consent screen, and approve the connection.
5. Start a new conversation and select Upstream from the tools menu.

This uses a custom MCP connection. It does not require a published ChatGPT app. See OpenAI's connection guide for current availability and settings.

Claude

1. Open Customize → Connectors and select + → Add custom connector.
2. Name it Upstream and enter https://studio.upstream.so/mcp.
3. Add the connector, select Connect, and sign in on Upstream to review and approve access.
4. Enable Upstream from the conversation's Connectors menu.

Custom connectors depend on your plan. Team and Enterprise owners must first add the connector for their organization. See Claude's custom connector guide.

Claude Code

claude mcp add --transport http --scope user upstream \
  https://studio.upstream.so/mcp

Open Claude Code, run /mcp, and select Upstream to authenticate. Sign in on Upstream and approve access, then run /mcp again to check the connection. See the Claude Code MCP guide.

VS Code

Shortened. The full README is on GitHub.