Common questions about connecting and using the Restream MCP server, organized by topic.
A server that connects your AI assistant directly to your Restream account, so you can manage streams in plain language instead of the dashboard — schedule streams, control destinations while live, and pull analytics, transcripts, and clips afterward.
No. Connecting MCP doesn't require a subscription — just a Restream account.
Add https://mcp.restream.io/mcp as a custom connector in your AI assistant. Full per-platform setup steps are at support.restream.io; technical docs at developers.restream.io/mcp-server.
Any assistant that supports MCP. Confirmed in active use: Claude, ChatGPT, Cursor, and Codex.
Create, schedule, and reschedule streams; add or remove destinations across 30+ platforms; turn channels on or off mid-broadcast; pull viewer and chat analytics; export transcripts, chat logs, and recordings; cut clips — all as natural-language requests instead of dashboard clicks.
The API supports it — a clips project can be created from a storage file, a public video URL, or an event recording. In practice, clip creation currently works most reliably from event recordings; worth confirming a storage-file source behaves as expected before relying on that path.
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.
It can read and summarize chat as it comes in. It can't post replies into chat on your behalf — there's no send-message capability exposed through MCP today.
Not yet — TikTok's chat API isn't currently supported through Restream's unified chat. Keep the native TikTok chat monitor open alongside your stream if you're broadcasting there.
Yes, platform-side, not Restream-side: LinkedIn requires 150+ followers; Instagram requires 1,000+ followers and a Professional account.
MCP mirrors whatever your account's own plan already allows — it doesn't unlock destinations beyond your plan's normal limits.
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.
Connect it directly by URL instead — add https://mcp.restream.io/mcp as a custom connector rather than searching a built-in directory listing.
Not yet — today's MCP surface covers scheduling, live destination control, and post-stream content. Studio-level control is on the roadmap.