Mux MCP Server

Mux is the video API behind a large share of the web's on-demand and live playback: you POST an asset, it transcodes, stores and serves it, and Mux Data reports on how playback actually went. This is the company's own MCP server for that API, published from the mux-ts SDK monorepo and released to npm as @mux/mcp.

Its design is unusual and worth understanding before you install it. Rather than exposing one MCP tool per API endpoint — which for an API this size would flood an agent's context — it uses Stainless's Code Mode scheme and exposes exactly two tools: a documentation search tool for querying the SDK surface, and a code tool where the agent writes TypeScript against the Mux SDK. That code executes in an isolated Deno sandbox with no filesystem access and network access granted only to the hosts the SDK calls. One tool call can therefore create an asset, poll for readiness, attach a playback ID and pull its view metrics, rather than five separate round trips.

Sandboxing runs locally by default, under a Deno runtime the package installs for itself; DENO_PATH points at your own binary where that install cannot work (Alpine, --omit=optional, blocked downloads). Setting --code-execution-mode=remote hands execution to an external sandbox service instead. A companion mcp-code-runner binary runs a single request through the same worker for platforms that execute caller code in their own VM.

Two ways to connect. Locally, npx -y @mux/mcp with MUX_TOKEN_ID and MUX_TOKEN_SECRET from your Mux dashboard, plus optional MUX_SIGNING_KEY and MUX_PRIVATE_KEY if your workflow needs signed playback IDs. Remotely, Mux hosts the server at https://mcp.mux.com, which authenticates over OAuth or an HTTP Basic header built from the same token pair. Apache-2.0.