# LiveReacting [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/LiveReacting/livereacting-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/livereacting

## Description
Run a 24/7 live stream of pre-recorded videos, or live stream a recorded video at a set time.

## Tools
Capabilities this server exposes over MCP:

- **list_destinations** — Your connected YouTube, Facebook, Twitch, LinkedIn, X and custom RTMP destinations
- **validate_destinations** — Checks a destination's connection still works, before you rely on it
- **list_projects** — Your projects
- **get_project** — One project's configuration
- **create_project** — A new project
- **update_project** — Change a project's settings
- **get_scenes** — Scenes in a project, or one scene
- **manage_scene** — Create, rename or delete a scene
- **activate_scene** — Switch the active scene, including during a broadcast
- **create_scene_with_playlist** — A scene plus its video playlist in one call
- **add_layer** — Add one video playlist, audio playlist or single video layer to an existing scene
- **get_layer** — One layer, with its playlist truncated for context
- **set_playlist** — Replace a playlist's contents
- **start_stream** — Go live
- **stop_stream** — End the broadcast
- **get_stream_status** — Live state, per destination, including expired connections
- **schedule_stream** — Go live at set times
- **cancel_schedules** — Cancel scheduled broadcasts
- **sync_stream** — Push editor changes to a running stream
- **list_broadcasts** — Past broadcasts for a project
- **list_media** — Files and folders in your library
- **get_media_file** — One file's details
- **upload_file** — Start uploading a local file: returns part URLs and curl commands
- **complete_upload** — Finish an upload once every part is sent
- **import_media** — Import from Google Drive, Dropbox or YouTube
- **import_from_url** — Import from a direct link to a media file on any public host
- **get_import_status** — Poll an import, including every video of a playlist import
- **encode_media** — Re-encode a file for streaming
- **get_encode_status** — Poll an encode
- **get_stream_analytics** — YouTube analytics, or per-video playlist analytics (that type on request)

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "livereacting": {
    "url": "https://mcp.livereacting.com/mcp"
  }
}
```

## Documentation

## What the LiveReacting MCP server does

The LiveReacting MCP server exposes LiveReacting account, editor, stream, media, and analytics functions to MCP-compatible clients. It is intended for workflows that prepare video playlists, operate broadcasts, inspect their status, and review results afterward.

Projects can be created and updated, with scenes added, renamed, removed, or activated. Scenes support video playlists, audio playlists, and individual video layers. An agent can also create a scene and its video playlist together, replace playlist contents, or apply editor changes to a running stream.

Broadcast controls cover immediate starts and stops, scheduled broadcasts, schedule cancellation, per-destination status, and a list of previous broadcasts. Connected destinations can be listed and validated for YouTube, Facebook, Twitch, LinkedIn, X, and custom RTMP endpoints.

## How it works

The LiveReacting MCP server is a stateless Streamable HTTP endpoint at `https://mcp.livereacting.com/mcp`. Requests are authenticated with a LiveReacting API key sent as a bearer token. The key is created in the Developer section of LiveReacting Studio and is available with paid plans; Free-plan API calls return a plan-access error.

Tools are grouped into account, editor, streams, media, and analytics toolsets. The endpoint accepts query parameters that can reduce the exposed surface. For example, `toolsets=streams,media` limits the toolsets, while `read_only=1` removes tools that change account data or broadcasts.

## Setup and configuration

Set `LIVEREACTING_API_KEY` in the shell environment or another secret store, then configure the remote MCP URL with an `Authorization: Bearer` header. Claude Code, Codex CLI, Cursor, VS Code with GitHub Copilot, Gemini CLI, Kiro, Zed, and Goose each have documented configuration approaches. Some can expand an environment variable or prompt for the key; avoid committing a real key to a repository.

The LiveReacting MCP server supports protocol revisions from `2024-10-07` through `2025-11-25`. A client reporting a protocol-version error should be checked against that range.

## Tools and capabilities

- List and validate connected streaming destinations.
- Create, inspect, and modify projects and scenes.
- Build video and audio playlists and manage supported layers.
- Start, stop, schedule, synchronize, and monitor streams.
- Browse media, upload local files through signed multipart URLs, and complete uploads.
- Import media from Google Drive, Dropbox, YouTube, or a public direct URL.
- Track imports and encoding jobs, re-encode media, and retrieve stream analytics.

Local uploads require a shell or HTTP client to send file parts to the URLs returned by `upload_file`; the agent then calls `complete_upload`.

## Limitations and notes

The LiveReacting MCP server can create and edit video and audio playlists, but text, image, and interactive layers must be authored or edited in LiveReacting Studio. Existing overlays can still be operated from MCP: streams can be started, stopped, scheduled, synchronized, and monitored.

A stream is subject to the maximum duration of its LiveReacting plan, including streams intended to run continuously. Analytics support YouTube data and per-video playlist analytics when that type is requested. Tool names are prefixed with `livereacting_` in clients that show the server's namespaced tools.

_Full upstream README: https://allmcps.com/mcp/livereacting/readme_