Skip to directory

About Mux MCP

Mux's hosted remote MCP exposes documentation search and a TypeScript execution tool backed by the Mux SDK, enabling clients to manage Mux Video and Data resources and query performance.

What you can use it for

  • Search Mux API and SDK documentation
  • Upload/manage videos and live streams
  • Analyze Mux Data performance, metrics, and dimensions
  • Inspect assets, playback IDs, tracks, and usage
Connection and setup
Hosting
both
Transport
Not documented
Endpoint
https://mcp.mux.com
Authentication
Hosted endpoint uses OAuth when the client supports it; user signs in to Mux Dashboard and chooses an environment. For non-OAuth clients use a Mux access token (ID and secret), locally via MUX_TOKEN_ID and MUX_TOKEN_SECRET or remotely as Basic authorization header.

Requirements

  • Mux account
  • MCP client supporting remote server and OAuth, or a Mux access token for clients without OAuth

Setup steps

  1. Add https://mcp.mux.com as a remote MCP server in the client.
  2. Complete Mux Dashboard sign-in and choose the environment for access.
  3. If OAuth is not supported, create a scoped Mux access token in Dashboard > Settings > Access Tokens and configure credentials securely.
  4. Start with documentation search or a read-only query. Restrict execute to read-only GET methods where supported.
Tools 2

Mux documents exactly two Code Mode tools matching stored names: search_docs and execute. execute runs TypeScript against the broad Mux SDK in an isolated hosted sandbox and inherits the authorized token’s permissions; use a read-only token to prevent writes.

  • search_docs

    Search Mux API and SDK documentation.

    01
  • execute

    Execute TypeScript code against the Mux SDK in an isolated hosted sandbox.

    02
Limitations and notes
  • The execute tool can reach the broad Mux SDK surface and is not inherently read-only; documentation says destructive operations are not specially restricted.
  • Hosted execution runs in a Mux-owned sandbox with network access limited to Mux API hosts.
  • Non-OAuth remote setup requires correct Basic authorization encoding of token ID and secret.
Original sources
  • official tool reference

    Mux documents exactly two Code Mode tools matching stored names: search_docs and execute. execute runs TypeScript against the broad Mux SDK in an isolated hosted sandbox and inherits the authorized token’s permissions; use a read-only token to prevent writes.

  • official documentation or source

    Mux documents exactly two Code Mode tools matching stored names: search_docs and execute. execute runs TypeScript against the broad Mux SDK in an isolated hosted sandbox and inherits the authorized token’s permissions; use a read-only token to prevent writes.

Documentation checked 2026-10-28T13:45:00.000Z. Connection has not been runtime tested.

Similar tools