Run your streams by asking

Stream Repeater has an MCP server, so Claude, Cursor, VS Code and other AI assistants can check your stream, go live, pause a destination, clip a moment or read chat when you ask them to, with your own API token and nothing that token could not do anyway.

Create an API token Setup guide →

Included on every plan. Works with any MCP client that can send a header.

Your AI assistantStream Repeater connected
  1. You: Is my stream healthy right now?
  2. Used get_channel_status · The Signal
  3. Assistant: Yes. The Signal has been live for 1 h 12 min at about 6 Mb/s with no packet loss. YouTube and Twitch are running; Kick is starting again after a drop. Want me to check it in a minute?
An example conversation. The tools are real; your assistant will word things its own way.

What it is, in plain language

MCP, the Model Context Protocol, is how AI assistants use other software. Connect ours once and your assistant can see and run your Stream Repeater workspace the same way you do in the dashboard.

  1. You ask

    Type what you want, the way you would ask a producer. No commands to learn.

  2. It uses your API

    The assistant picks the right tools, and each one calls the same API a script would, with the same permission checks.

  3. You stay in charge

    The server tells assistants to check with you before anything viewers would notice, and a read-only token cannot change anything at all.

Things you can ask

A few conversations, with the tools the assistant used along the way.

Pause one platform, keep the rest

Your AI assistantStream Repeater connected
  1. You: Pause YouTube for now but keep Twitch running.
  2. Used list_destinations · The Signal
  3. Assistant: Pausing YouTube ends the broadcast for viewers there. Go ahead?
  4. You: Yes.
  5. Used set_destination_enabled · YouTube → paused
  6. Assistant: YouTube is paused. Twitch and Kick are still live. Tell me when to bring it back.

Check your allowance

Your AI assistantStream Repeater connected
  1. You: How much bandwidth have I used this month? Will I run out?
  2. Used get_usage · Signal Media
  3. Assistant: You have used 182 GB of 500 GB. At about 9 GB a day you will end the month near 270 GB, well inside your allowance.

Clip a moment

Your AI assistantStream Repeater connected
  1. You: Clip the last 30 seconds and call it "Clutch round".
  2. Used create_clip · 30 s
  3. Assistant: Done. "Clutch round" is being cut from the live recording and will be in your clips in a moment.

Your keys stay yours

Your AI assistantStream Repeater connected
  1. You: What is my stream key? I need it for OBS.
  2. Used get_stream_keys · The Signal
  3. Assistant: I can only see a masked key, so I cannot read it out. Copy it from the channel page in the dashboard, under the connection details. The server address for OBS is fine to use as it is.

An example conversation. The tools are real; your assistant will word things its own way.

Everything your assistant can do

The server has 29 tools today. This list is read from the server itself, so it is always the current one.

Workspaces and health

5

What you have, whether it is healthy, and how much you have used.

  • list_workspaces Read-only

    Lists your workspaces, your role in each and its plan.

  • list_channels Read-only

    Lists channels with live status, the go-live switch, recording and destination counts.

  • get_channel_status Read-only

    Health of a stream: live or not, bitrate, uptime, packet loss, viewers and every destination's relay state.

  • get_usage Read-only

    Bandwidth used against your allowance, with a forecast.

  • get_stream_keys Read-only

    Server addresses for your encoder, with keys masked, and where to copy the real ones.

Going live and destinations

5

Switch a channel on or off, add, pause and resume platforms.

  • list_destinations Read-only

    Lists where a channel is relayed to, without URLs or stream keys.

  • go_live Makes changes

    Switches a channel's ingest on, so it relays to every enabled destination.

  • end_stream Makes changes

    Switches a channel's ingest off, ending the broadcast everywhere.

  • add_destination Makes changes

    Adds a destination from a connected account, a full URL, or a server and key.

  • set_destination_enabled Makes changes

    Pauses or resumes one destination.

Recordings and clips

5

Turn cloud recording on or off, list recordings and make clips.

  • list_recordings Read-only

    Lists a channel's cloud-recorded segments.

  • list_clips Read-only

    Lists a channel's clips, newest first.

  • start_recording Makes changes

    Turns cloud recording on for a channel.

  • stop_recording Makes changes

    Turns cloud recording off for a channel.

  • create_clip Makes changes

    Clips the last few seconds of the live recording, or cuts a clip from a recording.

Live chat

2

Read your unified chat and post in it.

  • get_recent_chat Read-only

    Reads recent messages from your unified live chat.

  • send_chat_message Makes changes

    Posts a message in your live chat on the connected platforms.

Podcast Rooms

12

Open or book rooms, see who is waiting, admit, mute, stage or remove guests.

  • list_podcast_rooms Read-only

    Lists a channel's Podcast Rooms: open, booked or past, with join codes and links.

  • get_podcast_room Read-only

    One Podcast Room: status, join link, and who is waiting or on air.

  • list_podcast_participants Read-only

    Lists the host and guests in a Podcast Room, waiting or on air.

  • get_podcast_settings Read-only

    A channel's Podcast Rooms defaults, branding and custom domain state.

  • start_podcast_room Makes changes

    Opens a Podcast Room now, or books one for later, and returns the join link.

  • end_podcast_room Makes changes

    Ends an open Podcast Room for everyone, or cancels a booked one.

  • admit_podcast_guest Makes changes

    Admits a guest from the waiting room.

  • deny_podcast_guest Makes changes

    Turns away a guest who is still waiting.

  • remove_podcast_guest Makes changes

    Takes a guest off air and out of the room.

  • mute_podcast_guest Makes changes

    Mutes or unmutes a guest in the host's mix.

  • stage_podcast_guest Makes changes

    Brings a guest on stage or sends them backstage.

  • update_podcast_settings Makes changes

    Changes a channel's Podcast Rooms defaults.

Full tool reference and client setup →

Safe to hand to an assistant

The assistant works through an API token you create and can revoke. It gets no more access than that token, and less than you have.

  • Read-only or full accessChoose when you create the token. A read-only token can check health, usage and chat but cannot change anything, and your workspace role still applies.
  • Keys are never sharedStream keys, destination URLs and passwords are never returned to an assistant. Connection details come back masked.
  • Every change is loggedEach change made through MCP appears in your workspace Activity log, naming the tool, the token and the person.
  • Asks before it actsThe server tells assistants to confirm with you before ending a stream, pausing a platform, posting in chat or admitting a guest.
  • Revoke any timeRevoke the token in Settings and the assistant loses access straight away. Each token is limited to 120 MCP requests a minute.
  • Chat treated as dataViewers write chat messages, so the server tells assistants never to follow instructions found in them.
The workspace Activity log: "An AI assistant made a change. AI assistant (MCP): opened a podcast room on The Signal, token Claude Desktop, by Jordan Blake"
What a change made by an assistant looks like in your Activity log.

Set up in three steps

  1. Create a token

    In Settings → API tokens, create a token for your assistant. Pick Read-only if it should only look.

  2. Add the server

    Give your MCP client the server address and the token. In Claude Code it is one command:

    claude mcp add --transport http streamrepeater \
  https://streamrepeater.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

  3. Ask

    Ask in plain language. The assistant finds your workspace and channels and picks the tools.

https://streamrepeater.com/mcpCopy-paste setup for Claude Desktop, Cursor, VS Code and other clients →

Works with the assistant you already use

Any MCP client that supports the Streamable HTTP transport and can send an Authorization header.

  • Claude DesktopThrough the mcp-remote bridge.
  • Claude CodeOne terminal command.
  • CursorA few lines in mcp.json.
  • VS CodeAsks for the token once and stores it securely.
  • Any MCP clientPoint it at the server URL and send the header.

Connectors added on the web, such as on claude.ai or in ChatGPT, sign in with OAuth rather than a pasted token, which this server does not offer yet.

Prefer to write the code yourself?

The assistant uses the same public API you can call from your own scripts and services.

REST API

131 operations covering channels, destinations, recordings, clips, chat, analytics and Podcast Rooms, described in OpenAPI 3.1.

curl https://streamrepeater.com/api/v1/channels \
  -H "Authorization: Bearer $TOKEN"
API reference →OpenAPI JSON

Webhooks

Get a signed POST when something happens, retried up to 6 times if your endpoint is down. Events include:

  • stream.live
  • stream.offline
  • destination.failed
  • recording.started
  • bandwidth.warning
Webhook docs →

For AI crawlers too

A plain-text summary of the product, the API and every MCP tool, for models that read the web.

llms.txt →

Questions

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants use tools in other apps. Stream Repeater runs an MCP server, so an assistant that supports MCP can work with your streams when you ask it to.

Which assistants work with it?

Claude Desktop, Claude Code, Cursor, VS Code and any other MCP client that supports the Streamable HTTP transport and can send an Authorization header. The setup page has copy-paste configuration for each.

Does it work in ChatGPT or on claude.ai?

Not yet. Connectors added on the web sign in with OAuth rather than a pasted token, and this server only accepts API tokens for now. Use a desktop or editor client in the meantime.

Can the assistant see my stream key?

No. Stream keys, destination URLs and passwords are never returned to an assistant. It gets masked connection details and is told where you can copy the real ones.

Can I let it look but not touch?

Yes. Create a Read-only token. The assistant can then check health, usage, recordings and chat, but every tool that changes something is refused.

How do I know what it changed?

Every change made through MCP is written to your workspace Activity log with the tool, the token and the person it belongs to.

Does it cost extra?

No. API tokens and the MCP server come with every plan. What a tool can do still depends on your plan: recording tools need a plan with recording, for example.

Does the assistant run all the time?

No. It only does something when you ask it to, in your assistant. Stream Repeater keeps relaying your streams by itself either way.

Give your assistant the keys to the control room, not the stream keys

Create a free workspace, make an API token and connect your assistant.

Start for free Read the setup guide →
14 days of Pro free, no card Start for free