← Explore all mcp servers

MEDIA MANAGEMENT / Mux

Mux MCP Server

Hosted Mux server built on the Code Mode scheme: a documentation search tool plus a code execution tool that runs agent-written TypeScript against the Mux TypeScript SDK (@mux/ts) in an isolated sandbox, covering Video, Data, Robots, System and Webhooks surfaces.

“The quickest way to get started is the remote server hosted at https://mcp.mux.com.”

01 / THE REASONING

Why this made the selection.

  • Mux hosts the server itself at mcp.mux.com with OAuth handled by the client negotiation, removing local install and token copying from the setup path.
  • Code Mode exposes two tools, search_docs and execute, instead of hundreds of endpoint tools, and each hosted execute call runs in a fresh, isolated Mux-owned sandbox whose network access is limited to Mux API hosts.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • Mux docs integration page, read 2026-10-13: remote server at https://mcp.mux.com, credentials on every request, OAuth via dashboard.mux.com with an environment choice, Basic credentials for clients without OAuth, Code Mode's two tools, the SDK surfaces reachable (Video, Data, Robots, System, Webhooks), sandbox network limits and the Read-permission token advice.
  • Mux local-installation page: the server is published to npm as @mux/mcp, runs execute in a local Deno sandbox limited to Mux hosts, and can restrict tools and SDK methods.
  • Mux remote MCP announcement post (22 August 2025): the remote server runs on Vercel Functions with WorkOS handling OAuth, built on Stainless's streamable HTTP support.
  • Mux MCP launch post (3 July 2025): the first public release, run locally.
  • Unauthenticated probes on 2026-10-13: a POST to https://mcp.mux.com answered HTTP 401 and a GET answered 405. (The 2026-10-07 review recorded 401 for GET on both https://mcp.mux.com and https://mcp.mux.com/mcp; /mcp now answers 404.)

Our findings

  • The execute tool runs agent-written TypeScript against @mux/ts; on the hosted server each call runs in a fresh, isolated Mux-owned sandbox with network access limited to Mux API hosts, and printed or returned output goes back to the agent.
  • A local npm variant (@mux/mcp) exists for clients without remote MCP support or that need to restrict which tools and SDK methods the server may run.
  • Corrected 2026-10-13: this record named the SDK @mux/mux-node, described a sandbox with no web access, and said the remote server exposed the Mux API minus some DELETE routes. The current docs name @mux/ts and network access limited to Mux API hosts; the DELETE-routes scope came from the July 2025 post about the first, locally run release.
  • configExample is the docs page's only JSON block, for clients that cannot do OAuth: Basic credentials with the page's own placeholder. OAuth clients enter only the URL https://mcp.mux.com.

Not established by this review

  • No OAuth authorisation was completed and no video or data operation was executed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Add https://mcp.mux.com as a remote MCP server in the client.
  2. Complete the OAuth login to dashboard.mux.com and choose which environment to authorise.
  3. To prevent changes, use an access token with only Read permissions instead: send it as Basic credentials (base64 of TOKEN_ID:TOKEN_SECRET in the Authorization header), or run the local @mux/mcp server with it.

Before you start

  • A Mux account.
  • An MCP client that supports remote servers with OAuth.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "mux": {
      "url": "https://mcp.mux.com",
      "headers": {
        "Authorization": "Basic <base64 of TOKEN_ID:TOKEN_SECRET>"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://www.mux.com/docs/integrations/mcp-server

    Supports: summary, upstreamDescription, install, configExample, access, whySelected, bestFor, limitations, compatibility

  2. https://www.mux.com/blog/remote-mcp

    Supports: whySelected, access, transports

  3. https://www.mux.com/blog/mux-mcp

    Supports: review

  4. https://www.mux.com/docs/integrations/installing-mcp-server-locally

    Supports: compatibility, limitations, review

Evidence & Ask