Mux MCP Server

Content

The Mux MCP Server is the official Model Context Protocol server for the Mux API, maintained by Mux. It gives LLMs and agentic clients access to Mux Video — assets, live streams, playback IDs, and direct uploads — and Mux Data — viewer and playback analytics — through the Mux SDK.

It ships as the npm package @mux/mcp (v14.1.1, Apache-2.0), runs over stdio via npx, and authenticates with a Mux access token (MUX_TOKEN_ID / MUX_TOKEN_SECRET). Rather than exposing one tool per API operation, it uses a Code Mode scheme: it presents a documentation-search tool and a code tool, and the agent writes TypeScript against the Mux SDK that runs in an isolated sandbox (no web or filesystem access), returning whatever the code prints or returns. Full setup lives in the mcp-server README.

Source Review

The following real repository and package sources were fetched and reviewed for this entry:

• mcp-server README — the npx install command, the MUX_TOKEN_ID/MUX_TOKEN_SECRET (and optional signing/webhook) env vars, the client config block, the Code Mode scheme, and the remote HTTP transport option.
• npm: @mux/mcp — package name and version (14.1.1), Apache-2.0 license, and the mcp-server bin entry.
• muxinc/mux-node-sdk — the official Mux Node SDK repository that hosts the MCP server package.

Repository facts confirmed at review time: official muxinc organization, default branch master, not archived, actively maintained, with the MCP server distributed as @mux/mcp v14.1.1 on npm.

Features

• Code Mode architecture — exposes a documentation-search tool plus a code tool that executes agent-written TypeScript against the Mux SDK in an isolated sandbox.
• Mux Video — work with assets, live streams, playback IDs, and direct uploads through the SDK.
• Mux Data — query viewer and playback analytics such as video views, errors, and quality metrics.
• Token authentication — authenticates with a Mux access token (MUX_TOKEN_ID / MUX_TOKEN_SECRET); optional signing/private keys and webhook secret for signed playback and webhooks.
• Sandboxed execution — the code tool runs without web or filesystem access, returning only what the code outputs.
• Deterministic complex tasks — because the agent writes SDK code, multi-step operations run repeatably.
• Remote transport — a --transport=http option runs the server over HTTP for remote clients.
• One-command install — runs via npx -y @mux/mcp@latest with no clone or build step.

Installation

Run the published package with npx, providing a Mux access token via environment variables:

export MUX_TOKEN_ID="your_token_id"
export MUX_TOKEN_SECRET="your_token_secret"
npx -y @mux/mcp@latest

Add it to an MCP client (e.g. Claude Desktop's claude_desktop_config.json):

{
  "mcpServers": {
    "mux": {
      "command": "npx",
      "args": ["-y", "@mux/mcp"],
      "env": {
        "MUX_TOKEN_ID": "your_token_id",
        "MUX_TOKEN_SECRET": "your_token_secret"
      }
    }
  }
}

Optional environment variables (MUX_SIGNING_KEY, MUX_PRIVATE_KEY, MUX_WEBHOOK_SECRET) enable signed playback URLs and webhook handling. Launching the client with --transport=http runs the server over HTTP for remote use.

Use Cases

• Video asset management — create, inspect, and manage Mux Video assets and uploads in natural language.
• Live streaming operations — set up and inspect live streams and playback IDs.
• Analytics queries — pull Mux Data metrics such as views, errors, and quality-of-experience for a title or time range.
• Deterministic automations — have the agent write SDK code for multi-step Mux workflows that run repeatably.
• Integration prototyping — explore the Mux API via the documentation-search tool while building an integration.

Safety and Privacy

• Code Mode runs agent-written code. The code tool executes TypeScript against the Mux SDK in a sandbox with no web or filesystem access, but it runs with your Mux token and can create, modify, or delete real resources.
• Token is the boundary. Scope the Mux access token to least privilege and prefer a non-production environment for autonomous agents.
• Signing keys are secrets. MUX_SIGNING_KEY / MUX_PRIVATE_KEY enable signed playback and JWTs; keep them and the token secret out of version control.
• Data flows to the model. Asset metadata and Mux Data analytics (including viewer/session information) are returned to the LLM/MCP client.
• Remote transport exposure. The --transport=http option opens a network listener; secure and authenticate it before exposing it beyond localhost.

Duplicate Check

No existing entry in the directory matches this server. A search of all directory entries for "mux" across slugs, titles, repository URLs, and install commands returned no results, and there is no prior entry pointing at github.com/muxinc/mux-node-sdk or the npm package @mux/mcp. This is therefore a net-new, non-duplicate entry.

• Source repositorygithub.com 2026-07-08T14:53:09-07:00
• Documentationgithub.com
• Websitemux.com
• Submitted by davion-knight2026-07-08