Restream

by Unknown

Not rated
Website

About

Connect Restream MCP to Claude or ChatGPT to create, schedule, manage, and analyze live streams across 30+ platforms.

Details

Author
Unknown
Categories
Communication, Other, AI, Productivity

Connect AI assistants and agents to a Restream account over theModel Context Protocol. The Restream MCP server is a remote, OAuth-secured server that exposes Restream's channel, event, destination, recording, storage, clips, and analytics capabilities as MCP tools, so an MCP client can read and operate a user's account on their behalf.

One-click installation from the Claude and ChatGPT connector directories is not available yet. Until then, add the server manually with the endpoint above. Setup is otherwise identical.

- A Restream account. Free accounts can connect channels and create events; some destinations and limits depend on plan.
- An MCP-capable client that supports a remote server.

The MCP server can create clip projects, create and reschedule events, remove events, and toggle destinations. Keep human confirmation enabled in your client and review write tool calls before approving them.

All clients point at the same endpoint:https://mcp.restream.io/mcp. The first tool call triggers the OAuth browser sign-in.

claude mcp add --transport http restream https://mcp.restream.io/mcp # Then authorize: /mcp

Settings -> Connectors ->Add custom connector:

- Name:Restream
- URL:https://mcp.restream.io/mcp

Enable Developer Mode in Settings -> Connectors -> Advanced settings, thenCreatea connector:

- Name:Restream
- MCP server URL:https://mcp.restream.io/mcp
- Authentication:OAuth

Add the server to~/.cursor/mcp.jsonfor global use or.cursor/mcp.jsonfor a project:

{ "mcpServers": { "restream": { "url": "https://mcp.restream.io/mcp" } } }
{ "servers": { "restream": { "type": "http", "url": "https://mcp.restream.io/mcp" } } }

In Settings -> MCP Servers, add a Streamable HTTP server namedrestreamwith URLhttps://mcp.restream.io/mcp.

Bridge with themcp-remoteshim, which handles the OAuth handshake:

{ "mcpServers": { "restream": { "command": "npx", "args": ["mcp-remote", "https://mcp.restream.io/mcp"] } } }

Client UIs change frequently. If a menu label differs from the steps above, check your client's MCP documentation.

Ask the assistant: "List my connected Restream channels." It should request permission to call the Restream tools and return your channels byplatformanddisplayName. If you see them, you are connected.

- The server implements OAuth 2.1; your MCP client performs the authorization-code flow in the browser and manages token refresh.
- Access is bound to the signed-in user. There is no separate API-key or bearer-token path for the MCP server. Authentication is OAuth only.
- For security, the MCP server deliberately will not:

- accept passwords, including account or channel logins;

- accept RTMP/SRT credentials to add custom channels;
- return stream keys or other internal IDs.

Perform those actions in thedashboardor via the REST API.

The server exposes 26 tools across six areas. Tools are taggedreadfor no side effects orwritefor actions that mutate account state. Your client should confirm before executing write tools.

Returns the authenticated user's profile and workspace context.

Lists channels connected to the account.

Checks every connected channel for platform API access issues and returns user-facing remediation steps for any that need attention.

Finds events across their lifecycle states.

Returns one event, including its active destinations.

Creates a Restream event from the user's chosen source, such as Studio, encoder, uploaded video, or saved recording.

Updates event details such as title and description.

Schedules a draft event or moves a scheduled one.

Removes the start time, turning the event back into a draft. External platform deletion stays disabled.

Removes the event from the Restream account. Only affects Restream state; it never deletes or modifies broadcasts or posts on external platforms.

Sets how many times a file- or recording-backed event repeats playback.

enable_event_external_scheduled_broadcasts - write

Enables creation and sync of scheduled broadcasts on supported external platforms for an already-scheduled event. This cannot be disabled through MCP.

Validates that the user's plan allows the selected channels to be active simultaneously and explains any plan limits.

Connects a channel as an event destination.

Disconnects a destination from an event. Affects Restream only; nothing is changed on the platform.

Updates platform-specific settings on an existing destination.

Lists recordings grouped by recording, with file names.

Returns a temporary download link for one recording file.

Lists clip projects for the authenticated account, with pagination and sort options.

Returns clips and posted clip information for one clip project.

Creates a clip project from a supported source. Currently, useVideoStorageFilesources discovered withlist_user_storage_files.

Creates a temporary download URL for one clip. Discover clip IDs withget_user_clips_project_detailsbefore requesting a download.

Returns viewer analytics for an event, with totals and per-channel values.

Returns chat-message analytics for an event, with totals and per-channel values.

Choose connected destinations, check plan limits, and prepare a Restream event for the selected platforms.

Create or update a scheduled event and sync broadcast details to supported platforms.

Create an event from stored media or a saved recording, with optional replay behavior.

Review viewer and chat activity after a stream.

Find a recording and provide temporary download access.

Find a video storage file, create a clip project, review generated clips and posted status, then provide a temporary download URL for the selected clip.

Connecting an LLM to an account that can create clip projects, create and remove events, and update destinations carries the usual agent risks. Recommended practices:

- Same-access principle:The MCP server operates as the signed-in user. Grant it only to people who should already have that access.
- Keep human confirmation on:Most clients prompt before each tool call. Leave this enabled and review write tool calls before approving them.
- Prompt injection:If an agent processes untrusted content, such as a webpage, chat message, or file, and that content contains instructions, the agent may try to act on them. Review planned actions before approving, and do not auto-approve write tools when untrusted input is in context.
- Removing destinations is non-destructive externally:toggle_event_channel_offandremove_eventonly change Restream state; they never delete or modify anything on the destination platforms.
- Verify the endpoint:Only connect to the officialhttps://mcp.restream.io/mcp.
- Credential boundary:The server never accepts passwords or RTMP/SRT credentials and never returns stream keys. Handle those in the dashboard or REST API.

- No password, RTMP/SRT credential entry, or stream-key retrieval.
- Not yet listed in the Claude or ChatGPT connector directories. Add the server manually with the endpoint above. Directory listings are coming soon.

A bridge server connecting Claude Desktop with the chakoshi moderation API for content safety.

Sends notifications from Claude Code with customizable sounds and cross-platform support.

Let Claude book a real restaurant table for you - an AI voice agent places the actual phone call, even to restaurants that only take reservations by phone.

Secure audio transcription meets AI. Connect Alice recordings to Claude, ChatGPT, Gemini, and more.

An MCP server to interact with OpenAI's ChatGPT API for conversational AI and text generation.

Local-first MCP server that puts your own LINE and Telegram chats behind one data layer — a daemon on your machine logs in with your own account, stores messages to JSONL + SQLite/FTS5, and exposes them to MCP clients like Claude Code. Not an npx one-liner: you clone the repo and run the daemon yourself.

An AI-powered email intelligence platform that integrates with Gmail and OpenAI. It can be run as a CLI tool or deployed on AWS Lambda for enhanced capabilities.

Integrate with Google's Gemini AI models for various tasks.

An intelligent, LLM-powered email assistant using the Nylas v3 API.

A chat assistant that integrates an MCP client with an LLM and other external MCP servers.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.