MCP server · Content and web

Mux MCP server

Mux in any MCP client, through Memtro: Mux does not publish this server. Memtro's Mux connector reads Mux through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Mux video platform: video assets with status, duration, resolution, quality and public playback ids, live streams and their status, delivered minutes per asset, and Mux Data playback analytics (views, metrics such as viewer experience, startup time, rebuffering and failures, open incidents and top player errors); when you ask, can update, create (billed) or delete assets and their playback ids, create, enable, disable, complete or delete live streams, cancel uploads, and add, edit or delete Data annotations.

Reads

  • mux_list_assetsVideo assets in this Mux environment, in the order Mux returns them: id, title, status (preparing, ready, errored), created, duration, resolution…
  • mux_get_assetOne Mux video asset in full: status, duration, resolution, quality, public playback ids, tracks (video, audio, subtitles with language)…
  • mux_list_live_streamsLive streams in this Mux environment: id, title, status (active, idle, disabled), the asset recording now and recent ones, latency mode…
  • mux_delivery_usageMinutes of video delivered (streamed to viewers) per asset in a window, with the split by resolution tier and the asset's duration…
  • mux_video_viewsIndividual playback views from Mux Data that ended in a window (default the last 7 days): video title, start and end, watch time…
  • mux_metricOne Mux Data metric over a window (default the last 7 days) with the total views, watch time and playing time behind it: views, unique viewers…
  • mux_incidentsMux Data incidents (alerts and warnings raised when a playback metric crossed a threshold): description, status (open, closed, expired), severity…
  • mux_errorsThe player errors Mux Data saw in a window (default the last 7 days): error code and message, how many views hit it and what share of views…

Acts, when you ask

These change something in Mux. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • mux_update_assetChanges a Mux video asset's title, external id, passthrough or default thumbnail time; nothing else about the video changes.
  • mux_create_assetCreates a Mux video asset by having Mux download a file from a public URL and encode it.
  • mux_delete_assetPermanently deletes a Mux video asset; it stops playing everywhere it is embedded and cannot be recovered.
  • mux_create_playback_idAdds a playback id to a Mux asset.
  • mux_delete_playback_idDeletes a playback id from a Mux asset; links and embeds using it stop working (a viewer already watching may finish).
  • mux_create_live_streamCreates a Mux live stream that an encoder can broadcast to.
  • mux_enable_live_streamEnables a disabled Mux live stream so encoders can connect and broadcast again.
  • mux_disable_live_streamDisables a Mux live stream: an active broadcast is cut off and its recording ends now, and encoders are refused until it is enabled again.
  • mux_complete_live_streamTells Mux the current broadcast on a live stream is finished, ending it and its recorded asset without waiting for the reconnect window.
  • mux_delete_live_streamPermanently deletes a Mux live stream; its stream key and playback ids stop working.
  • mux_cancel_uploadCancels a Mux direct upload that has not finished, so its upload URL stops accepting a file.
  • mux_create_annotationAdds an annotation to Mux Data charts at a date and time (a release, a CDN change, an incident), visible to everyone in the environment.
  • mux_update_annotationRewrites a Mux Data annotation's note and date (both are required by Mux).
  • mux_delete_annotationPermanently deletes a Mux Data annotation.

Connect it

First connect Mux on Dashboard → Connections, then add Memtro to your client once. The Mux tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Mux connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which player errors did viewers hit most this week?
  • › What is our median startup time over the last 7 days?
  • › Are there any open Mux Data incidents?
  • › Which assets delivered the most minutes yesterday?
  • › Change the title of the launch video to Spring Launch 2026.

Questions

Is this an official Mux MCP server?
No. It is Memtro's MCP server with Memtro's Mux connector behind it: the connector reads Mux through its API with the credentials you connect on Dashboard → Connections, and Mux publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Mux?
Only when you ask, and only what it has been granted: update a video asset's title, external id, passthrough or thumbnail time; create a video asset from a file URL (billed for encoding, storage and delivery); delete a video asset permanently; add a public or signed playback id to an asset; delete an asset's playback id; create a live stream (billed while streaming); enable a live stream; disable a live stream, ending any broadcast; signal that a live stream's broadcast is complete; delete a live stream permanently; cancel a direct upload; add a Mux Data annotation; update a Mux Data annotation; delete a Mux Data annotation. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Content and web

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time