Livepeer MCP. Manage full video pipelines from your chat client.

Livepeer manages your whole decentralized video pipeline. You're gonna use this MCP Server to handle everything from uploading raw assets and setting up live broadcasts, to generating short clips and tracking viewership numbers—all through conversation with your AI agent.

Asset Ingestion and Management

To start working with video, you gotta get the assets into Livepeer first. You can list every asset already stored in your account's library using list_assets. If you need details on a specific file, get_asset pulls all that metadata for you. For bringing content in, you have two main options: you can use request_asset_upload to get a direct, temporary URL from Livepeer and start the upload process there, or if your asset is already hosted somewhere else (like HTTP, IPFS, or Arweave), you just run upload_asset_via_url.

Once you're done with an asset—whether it's old garbage or something that broke—you can delete it using delete_asset.

Stream Setup and Control

Setting up your stream is where the magic happens. To start a totally new, dedicated live broadcast session, you run create_stream. If you need to shut down an active feed immediately, you use terminate_stream, which forces the cleanup of any running session. For advanced distribution, you can create a multi-platform target using create_multistream_target if you want one source beamed out to places like YouTube or Twitch; you'll then manage those settings by calling update_multistream_target and check their config with get_multistream_target.

To deal with private meetings, you can establish a new WebRTC multi-participant room using create_room, and then add specific users to that meeting via create_room_user. You'll need to update the stream settings—like changing the title or bitrate—by running update_stream, and check the status of any active feed with get_stream or see a list of all your streams (active or paused) using list_streams.

The room you created can even broadcast its output out to a standard live platform (RTMP) by calling start_room_egress. You can also delete an entire multi-platform target setup using delete_multistream_target.

Content Processing & Clipping

Don't let great footage sit there. If you want to pull a short segment out of an ongoing live broadcast, run create_clip, which generates that timestamped clip instantly. For background processing—say, converting your raw footage into multiple formats or resolutions for on-demand use—you schedule the job with create_transcode_job. You can track the progress and see if it succeeded or failed by running get_task against a specific job ID, and you get a list of all past jobs using list_tasks.

When you're done with your content management, remember you can also delete any associated assets via delete_asset.

Real-Time Analytics Retrieval & Monitoring

This is how you see if people are actually watching. To get the live count of viewers connected to a stream right now, use get_realtime_viewership. For historical data on who's watching—like breakdowns by device type or location—you run get_viewership_metrics. You can figure out your overall operational costs and usage numbers (total minutes transcoded, data delivered) using get_usage_metrics.

To check the details of past broadcasts, you list all finished sessions with list_sessions then pull specific info for one session ID using get_session. If that session created clips, you can see a list by running get_session_clips. For persistent notifications about what's happening in your infrastructure (like when an asset finishes processing), you set up a callback URL with create_webhook, monitor its details with get_webhook, and clean it up later using delete_webhook.

Other Tools You Need to Know

To keep everything organized, you can list all past broadcast sessions that have wrapped up by running list_sessions. If you need the necessary URLs or metadata just to play back a specific asset or stream, get_playback_info gives it to you. Finally, if you're managing your webhooks and need to change their destination parameters, use update_webhook, and likewise, if you want to modify an existing multi-platform target's keys or URLs, you run update_multistream_target.