How do I install the LiveReacting MCP server?

Configure your MCP client to use https://mcp.livereacting.com/mcp and send a bearer token from LIVEREACTING_API_KEY. The repository documents setup for Claude Code, Codex CLI, Cursor, VS Code, Gemini CLI, Kiro, Zed, and Goose.

Does LiveReacting work with Cursor?

Yes, LiveReacting works with Cursor through its remote MCP configuration or the LiveReacting Cursor plugin. Cursor can resolve LIVEREACTING_API_KEY in the Authorization header, keeping the key out of the configuration file.

What LiveReacting plan do I need for API access?

API access requires a paid LiveReacting plan. A Free-plan account using an API key receives a 403 API_ACCESS_REQUIRES_PAID_PLAN response, while the tools become available after the account is upgraded.

Can LiveReacting upload local video files?

Yes, but the agent needs a shell or HTTP client to send the file data. The upload_file tool returns multipart URLs and curl commands; after all parts are sent, complete_upload finishes the upload.

LiveReacting

live-streamingvideobroadcastingmediaanalytics

Control LiveReacting projects, media, scheduled broadcasts, destinations, and stream analytics through MCP.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Remote HTTP

Configure Environment Variables (API Keys, Tokens, Options):

Add required secrets below — values are included directly in the generated snippet so you can copy and paste with confidence.

Quick Add:

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "livereacting": {
      "url": "https://mcp.livereacting.com/mcp",
      "env": {
        "LIVEREACTING_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

The LiveReacting MCP server connects AI agents to LiveReacting over authenticated Streamable HTTP. It lets agents create and configure projects, manage video and audio playlists, import or upload media, start or schedule broadcasts, monitor destinations, and retrieve analytics. Reach for it when an agent needs to operate a LiveReacting channel without manually using Studio for each broadcast task. API access requires a paid LiveReacting plan and an API key.

Use cases

Create a project with a video playlist

Schedule a broadcast for connected destinations

Monitor stream status during a live broadcast

Import and encode media for streaming

Review YouTube or playlist analytics

Key features

Project and scene management

Video and audio playlist editing

Broadcast start, stop, and scheduling

Media upload, import, and encoding

Destination validation and stream status

Stream analytics retrieval

Capabilities & Tool Schemas (30)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by LiveReacting.

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

How LiveReacting works

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.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit

11d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about LiveReacting

LiveReacting is an MCP server that connects AI agents to LiveReacting through Streamable HTTP. Its main tools manage projects, scenes, video and audio playlists, media imports and uploads, streaming destinations, broadcasts, schedules, stream status, and analytics. Authentication uses a LiveReacting API key, available for accounts on paid plans.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/livereacting?style=directory)](https://allmcps.com/mcp/livereacting)

HTML Embed

<a href="https://allmcps.com/mcp/livereacting"><img src="https://allmcps.com/api/badge/livereacting?style=directory" alt="LiveReacting on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

52Quality signal: Good · 52/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools25/30

Adoption & activity4/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to LiveReacting →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients