Integration

Mux integration

Mux Video API for video streaming and hosting. Upload, transcode, and deliver video content with adaptive bitrate streaming. Create assets from URLs or direct uploads, manage live streams, and generate playback URLs. Supports HLS streaming, signed URLs for protected content, and DRM. Ideal for video platforms, streaming applications, and media delivery.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Mux.Built from the 16 Mux tools below, on the connection you add once.

Common Mux use cases

  • status checking
  • metadata updates
  • video upload
  • live streaming
  • stream cleanup
  • browser uploads
  • content removal
  • upload tracking
  • access revocation
  • stream monitoring

What you can do with Mux

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Asset, 5 operations

  • create_assetCreate assetPOSTCreates a video asset from a URL. Mux transcodes it for adaptive streaming.
  • delete_assetDelete assetDELETEPermanently deletes a video asset and all its playback IDs.
  • get_assetGet assetGETRetrieves complete details of a video asset including status, playback IDs, and encoding info.
  • list_assetsList assetsGETLists all video assets with pagination support.
  • update_assetUpdate assetPATCHUpdates mutable properties of a video asset like passthrough metadata.

Live stream, 5 operations

  • create_live_streamCreate live streamPOSTCreates a live stream with RTMP ingest URL for broadcasting.
  • delete_live_streamDelete live streamDELETEPermanently deletes a live stream and its playback IDs.
  • get_live_streamGet live streamGETRetrieves complete details of a live stream including status and stream key.
  • list_live_streamsList live streamsGETLists all live streams with optional status filtering.
  • update_live_streamUpdate live streamPATCHUpdates mutable properties of a live stream such as latency mode, reconnect window, and passthrough metadata.

Upload, 4 operations

  • cancel_uploadCancel uploadPUTCancels a pending direct upload, invalidating the upload URL.
  • create_direct_uploadCreate direct uploadPOSTCreates a direct upload URL for browser-based video uploads without exposing API credentials.
  • get_direct_uploadGet direct uploadGETRetrieves the status and details of a direct upload.
  • list_uploadsList uploadsGETLists all direct uploads with their status and resulting asset IDs.

Playback id, 2 operations

  • create_playback_idCreate playback idPOSTCreates a new playback ID with specified access policy (public, signed, or DRM).
  • delete_playback_idDelete playback idDELETERemoves a playback ID, disabling that streaming URL.

Mux API rate limits

  • 1 request per second

POST requests: 1 req/sec sustained with burst. GET/PUT/PATCH/DELETE: 5 req/sec sustained. HTTP 429 when exceeded. Limits are per account.

These are the limits Mux documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Mux documentation for current values.

Use Mux from Claude Code, Cursor or Codex

Connect Mux in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Mux operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Mux

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Mux once

    Add your Mux connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Mux integration FAQ

What can you do with the Mux integration?

LiveContext exposes 16 operations on Mux, covering asset, live stream, upload and playback id. Common uses include status checking, metadata updates and video upload.

What are the Mux API rate limits?

Mux documents 1 request per second. POST requests: 1 req/sec sustained with burst. GET/PUT/PATCH/DELETE: 5 req/sec sustained. HTTP 429 when exceeded. Limits are per account. Limits are set by Mux and can depend on your plan.

Popular integrations

Browse the whole catalog