Common questions about connecting and using the Restream MCP server, organized by topic. If you're new here, start with “What is Restream MCP?” and then jump to the section for how you stream.
Restream MCP is a server that connects your AI assistant directly to your Restream account. Instead of clicking through the dashboard, you ask in plain language: schedule a stream, turn a destination on or off while you're live, or pull viewer analytics, transcripts, chat logs, recordings and clips after the stream. It runs at https://mcp.restream.io/mcp and works with any AI assistant that supports MCP.
MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude, ChatGPT and Cursor securely connect to outside tools and services. Restream MCP is Restream's official MCP server. When you connect it, your assistant gains a set of Restream tools it can call on your behalf, with your permission and only within your account.
Yes. Connecting Restream MCP doesn't require a paid subscription, just a Restream account. The MCP server mirrors whatever your plan already allows: if your plan supports two destinations, MCP can control two destinations. It doesn't unlock features beyond your plan.
It depends on your assistant:
https://mcp.restream.io/mcp and authorize in the chat.https://mcp.restream.io/mcp as a custom connector or remote MCP server.Step-by-step instructions for each app are on the Connect page and in the Help Center; technical docs are at developers.restream.io/mcp-server. Once connected, try: “List my connected channels.”
Any assistant that supports MCP. There are step-by-step guides for Claude (Claude.ai, Claude Desktop and Claude Code), ChatGPT, Grok, Grok Bot, Muse, Cursor, VS Code with GitHub Copilot, and Codex. Clients that only support stdio can connect through mcp-remote. See Connect.
Yes. Restream is listed in the Claude connector directory, so there's nothing to copy or paste. Open claude.ai/directory/restream, click Connect, and sign in with your Restream account. Claude Code users can run claude mcp add --transport http restream https://mcp.restream.io/mcp.
Yes. Turn on Developer mode in Settings → Security and login, then go to Settings → Plugins → Browse plugins, click the + icon, add https://mcp.restream.io/mcp and sign in with your Restream account when prompted. See Connect in ChatGPT for the exact steps.
Yes. In Cursor, Restream is available directly: open Customize from the left sidebar, search for Restream and click Add, with no config file to edit. In VS Code with GitHub Copilot, add the server to .vscode/mcp.json with the URL https://mcp.restream.io/mcp. Configuration snippets are on the Connect page.
Yes, and you can set it up from the chat. Ask Muse to connect https://mcp.restream.io/mcp; Muse adds the server, asks you to authorize your Restream account, and finishes the setup in the same conversation, with no settings to open and nothing to paste. Then ask “List my connected channels” to confirm it's working. Step-by-step guide: Connect in Muse.
Muse shows a Restream sign-in prompt right in the chat. Sign in with your Restream account and approve access. Once you do, the connection is complete and you can start asking Muse about your streams in the same conversation.
Yes. In Grok Bot, Restream has its own plugin page: click Add and sign in. In Grok, go to Plugins → New connector → Custom and paste https://mcp.restream.io/mcp. Restream also publishes ready-made Grok Bot templates for live-chat research, stream analytics, transcripts and archiving.
Yes. Schedule every Sunday for the month in one conversation, set the sermon title for each week, confirm that Facebook and YouTube are ready to go live, and on Monday ask for the recording link to post on your website. You can also pull the transcript to turn into sermon notes. Works on the free plan. See the Schedule and Go live examples on the Examples page.
Yes. If Twitch keeps dropping mid-stream, tell your assistant to pull it from the event and bring it back when it's stable, without alt-tabbing out of your game. Check live viewer counts per platform, see which chat is most active, and after the stream create a clips project from the recording. See the Go live and Clips examples on the Examples page.
Yes. After a live episode, ask for the transcript to draft show notes, export the chat log as listener questions, and create a clips project from the recording to cut promo clips. Then schedule next week's episode to the same destinations in the same conversation. See the Analytics and Clips examples on the Examples page.
Yes. Schedule a whole cohort's sessions at once, reschedule a session when plans change, export the chat log as a Q&A record, and hand students the recording link afterward. Teams that work in Cursor or VS Code can run all of this from their editor.
Yes, from uploaded video files or past recordings. Ask your assistant what's in your storage, create a recording-backed event from a file, and set a loop count so it repeats. See the Schedule examples on the Examples page.
Yes. Before a company broadcast, run a pre-flight check: your assistant confirms your plan allows the chosen destinations, checks each channel's connection for platform issues, and tells you how to fix anything that's blocking LinkedIn or another destination. Afterward, pull viewer analytics by platform for your report and export the full chat log for your records.
Yes. Schedule a full day or weekend of sessions, reschedule on the fly when a match or set runs long, and ask for viewer numbers per platform after each session. You can also turn on native scheduled-broadcast sync, so supported platforms such as YouTube show the event in their own schedules.
Yes. Each connection is scoped to one Restream workspace. Ask “Which workspace is this assistant connected to?” at any time to confirm. To manage a different workspace, disconnect and reconnect while that workspace is active in your browser.
Create, schedule, reschedule, unschedule and remove events; edit titles and descriptions; add, configure, enable and disable destinations across 30+ platforms; turn channels on or off mid-broadcast; check that your plan allows the chosen destinations; check channel connection health; pull viewer and chat analytics; read chat messages and export the full chat log; get transcripts and recording download links; create clips projects and download clips; review your video storage; and confirm which workspace is connected. The server exposes 30 tools in total; the full list is in the tool reference. All of this happens through natural-language requests instead of dashboard clicks.
Restream MCP schedules events and controls destinations. The video itself still comes from Restream Studio, your encoder (such as OBS), or an uploaded file. Once your source is sending video, your assistant can turn individual destinations on or off, check viewers, and manage everything around the broadcast.
Yes. OBS keeps streaming to Restream exactly as it does today. Restream MCP handles the Restream side: scheduling, destination settings, turning channels on and off, analytics and post-stream content. You don't need to change anything in OBS.
Yes. Ask for the transcript and your assistant can summarize the whole stream or a specific part, for example “Summarize what I said in the first 10 minutes.” For long streams, ask for just the portion you need so it fits your assistant's context.
Yes. You can create a clips project from an event recording, a file in your storage, or a public video URL. Tell your assistant which source to use.
Yes. Connecting a channel as an event destination (YouTube, LinkedIn, Twitch and others) is supported through MCP. Some platforms require a title or other field before they'll accept the connection; your assistant can fill in the missing field and try again.
It can read and summarize chat as it comes in and report chat activity by platform. It can't post replies into chat on your behalf.
The MCP server operates as the signed-in user and never beyond your account's own permissions. Connection uses OAuth; there is no API key or bearer token to copy or leak. Every tool is tagged read or write, and your assistant should confirm with you before running a write tool such as removing an event. Removing an event never touches broadcasts or posts on external platforms. There are no tools to post to chat, change your Restream password or billing, or reach other workspaces. Only connect to the official endpoint https://mcp.restream.io/mcp. Details: Security.
Use Restream MCP when an AI assistant or agent is doing the work on your behalf in plain language. Use the Restream API when you're building an application or integration in code. Both operate on the same account and the same data. You can use both: MCP for day-to-day operations, the API for custom tooling.
No. TikTok chat isn't supported through Restream's unified chat. Keep the native TikTok chat monitor open alongside your stream if you're broadcasting there.
Yes, on the platform side, not the Restream side. LinkedIn requires 150+ followers. Instagram requires 1,000+ followers and a Professional account. Make sure your accounts meet these before you add them as destinations.
MCP mirrors whatever your account's own plan already allows. It doesn't unlock destinations beyond your plan's normal limits.
No. Restream MCP covers scheduling, live destination control, analytics and post-stream content. Scenes, layouts and guests are managed in Restream Studio.
The connection is scoped to whichever Restream workspace was active in your browser at the moment you approved it. Switching workspace afterward in the browser doesn't change what the assistant sees. Disconnect and reconnect while the correct workspace is active.
Restream is listed in Claude and Cursor, and has its own plugin page in Grok Bot. If search doesn't find it, go straight to the listing:
https://mcp.restream.io/mcp as a custom connector instead.Muse doesn't need a directory: just ask it to connect https://mcp.restream.io/mcp. In ChatGPT, Grok, Codex, VS Code and other clients, connect by URL: add https://mcp.restream.io/mcp as a custom connector or MCP server.
Ask it to check the event's channels. It confirms your plan allows the chosen destinations and checks each channel's connection for platform issues, with steps to fix anything it finds, such as a missing title or an expired connection. If a channel's connection has expired, reauthorize it in the Restream dashboard, then ask your assistant to check again.
Join the Restream Discord or open an issue on GitHub. Tell us what you tried to ask your assistant and what it couldn't do.