The Mux MCP for teams that automate video
Connect Mux once and your video assets, playback IDs, live streams, direct uploads, and Mux Data analytics become building blocks for visual automations and AI agent workflows. 32 nodes over the Mux Video and Mux Data APIs.
What the Mux MCP connector does
The Mux connector for Mattering Automations covers the core of the Mux Video and Mux Data APIs: ingest video assets from a URL, create and retire playback IDs, run live streams end to end (create, enable, disable, signal complete, and reset stream keys), create direct upload URLs for your own apps to use, and read Mux Data analytics, from individual video views to metric breakdowns, timeseries, and playback error lists. That is 32 nodes in total: 16 read nodes and 16 action nodes.
Mux has four kinds of IDs that look alike and get confused constantly: asset IDs, playback IDs, upload IDs, and live stream IDs. The ID in a stream.mux.com URL is a playback ID, not an asset ID, and pasting one where the other belongs is the most common Mux mistake there is. This connector treats that as a first-class problem: every ID field says exactly which ID it takes, and Mux: Resolve Playback ID exists purely to walk a playback ID back to the asset or live stream that owns it.
Each capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, and they also power Matter, the platform's built-in AI assistant. Describe the video workflow you want in plain language and it gets built on the canvas in front of you, where you can see every step and change it.
Mux bills on usage: encoding, storage, and streaming cost real money on your Mux account, so the nodes that create assets or run live streams say so in their descriptions. For building and rehearsing workflows, Mux's test mode (a test flag on asset, live stream, and upload creation) produces free, watermarked objects that Mux caps and deletes automatically, so you can prove a workflow end to end before it spends encoding minutes.
One connection, three surfaces
- Visual automations. Drag Mux nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Mux node, ready to drop on the canvas
32 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 16
Mux: Get Asset
Fetch a single video asset by its asset ID: status, duration, tracks, playback IDs, metadata.
Mux: Get Asset Input Info
Fetch details about an asset's ingest source files: container format, tracks, and the input settings used.
Mux: Get Asset Playback ID
Fetch one playback ID on an asset (its policy and value). Takes both the asset ID and the playback ID.
Mux: Get Direct Upload
Fetch a direct upload by its upload ID. Once status is asset_created, the created asset's ID is in data.asset_id.
Mux: Get Live Stream
Fetch a single live stream by its live stream ID: status, stream key, playback IDs, settings.
Mux: Get Live Stream Playback ID
Fetch one playback ID on a live stream (its policy and value). Takes both the live stream ID and the playback ID.
Mux: Get Video View
Fetch every collected field for a single video view by its view ID (the id from Mux: List Video Views).
Mux: List Assets
List video assets in the Mux environment, newest first. Filterable by source live stream or direct upload. Clean auth probe: works with no parameters.
Mux: List Direct Uploads
List direct uploads and their statuses: waiting, asset_created, errored, cancelled, timed_out.
Mux: List Live Streams
List live streams in the Mux environment (paginated).
Mux: List Playback Errors
List playback errors seen across video views in a timeframe, with counts and percentages.
Mux: List Video Views
List individual playback sessions (video views) from Mux Data, filterable by viewer, error, dimension filters, and timeframe. Requires Mux Data permission on the access token.
Mux: Metric Breakdown
Break a Mux Data metric down by a dimension, e.g. video_startup_time by country or by video_title.
Mux: Metric Overall Values
Get the overall value of a Mux Data metric for a timeframe, plus total views and watch time.
Mux: Metric Timeseries
Get a Mux Data metric over time as a series of intervals, e.g. rebuffer_percentage per hour for the last day.
Mux: Resolve Playback ID
Look up which asset or live stream a playback ID belongs to. Use this when you only have the playback ID from a URL and need the owning object's ID.
Action nodes 16
Mux: Cancel Direct Upload
Cancel a direct upload that is still waiting for a file. Only succeeds while the upload status is waiting.
Mux: Create Asset Playback ID
Create a new playback ID on an asset. The returned data.id is the playback ID to use in stream.mux.com playback URLs.
Mux: Create Asset from URL
Ingest a video into Mux from a publicly reachable file URL. Returns the new asset in status preparing; poll Mux: Get Asset (or use webhooks) until status is ready. Encoding is billable.
Mux: Create Direct Upload URL
Create a direct upload slot and get back a signed URL. Your own client or browser then PUTs the video file to that URL; this node does not upload the file itself. The finished asset's ID appears on the upload as asset_id once processed.
Mux: Create Live Stream
Create a live stream. Returns the stream key for the RTMP encoder plus a playback ID for viewers. Active streaming is billable.
Mux: Create Live Stream Playback ID
Create a new playback ID on a live stream for viewers. The returned data.id goes in the stream.mux.com playback URL.
Mux: Delete Asset
Permanently delete a video asset and all of its playback IDs. Irreversible: the video cannot be recovered.
Mux: Delete Asset Playback ID
Delete a playback ID from an asset. Every playback URL using that playback ID stops working immediately.
Mux: Delete Live Stream
Permanently delete a live stream and its stream key. Already-recorded assets are kept but the stream itself cannot be recovered.
Mux: Delete Live Stream Playback ID
Delete a playback ID from a live stream. Every playback URL using that playback ID stops working immediately.
Mux: Disable Live Stream
Disable a live stream: any active broadcast ends and new RTMP connections are refused until re-enabled.
Mux: Enable Live Stream
Enable a disabled live stream so it accepts an incoming RTMP connection again.
Mux: Reset Stream Key
Generate a new stream key for a live stream. The old key stops working immediately: any encoder still configured with it can no longer broadcast.
Mux: Signal Live Stream Complete
Signal that the broadcast is over: closes out the live playback (EXT-X-ENDLIST) without waiting for the reconnect window.
Mux: Update Asset
Update an asset's passthrough or meta metadata. Video content itself is immutable after ingest.
Mux: Update Live Stream
Update a live stream's settings: passthrough, latency mode, reconnect window, max duration, or new-asset settings.
Connecting Mux takes one credential
Mux authenticates with an access token sent as HTTP Basic auth: the Token ID is the username and the Token Secret is the password. You create tokens in the Mux dashboard under Settings, then Access Tokens. Each token is scoped to one Mux environment and carries separate permission toggles for Mux Video and Mux Data, and the Token Secret is shown once at creation.
In the Mux dashboard, open Settings, then Access Tokens, and generate a new token in the environment you want to automate.
Give it Mux Video permission, and add Mux Data permission if you want the analytics nodes. Copy both the Token ID and the Token Secret: the secret is shown only once.
In Mattering Automations, open Connectors, click Add Connector, and choose Mux.
Create a new credential with the Token ID as the username and the Token Secret as the password, then save. Credentials are stored encrypted in Google Secret Manager and never appear in workflow logs.
Connect the connector, then drop Mux: List Assets onto a canvas and run it. It takes no parameters and returns the assets in the token's environment, which confirms the credential works. All 32 Mux nodes are now in your palette.
Common uses for the Mux MCP
Publish a video from anywhere a URL exists
When a finished file lands at a public URL (a render pipeline, a cloud bucket, a form submission), Mux: Create Asset from URL ingests it, a loop polls Mux: Get Asset until the status is ready, and Mux: Create Asset Playback ID mints the ID that goes in the stream.mux.com playback URL. The finished link can then post itself to a task or a channel in the same workflow.
Run a live stream end to end
Mux: Create Live Stream returns the stream key for the broadcaster's encoder and a playback ID for viewers. Workflows can enable and disable the stream around a schedule, close out playback cleanly with Mux: Signal Live Stream Complete when the broadcast ends, and rotate a leaked key with Mux: Reset Stream Key. Resetting kills the old key instantly, so keep it a deliberate step, not a routine one.
Hand upload slots to your own product
Mux: Create Direct Upload URL creates an upload slot and returns a signed URL that your own app or browser PUTs the file to; the node itself never touches the file bytes. A follow-up workflow watches Mux: Get Direct Upload until the status reads asset_created, picks the new asset ID off the result, and carries on with playback IDs and notifications.
Watch playback quality before viewers complain
Mux: Metric Timeseries pulls a metric like rebuffer percentage hour by hour, Mux: Metric Breakdown splits video startup time by country or by video title, and a condition node raises an alert when a number crosses your threshold. Attach Mux: Metric Overall Values for the same timeframe so the alert arrives with the trend, not just the spike.
Triage playback errors with evidence attached
Mux: List Playback Errors returns the errors seen across views in a timeframe with counts and percentages, Mux: List Video Views finds the sessions that hit one, and Mux: Get Video View pulls every collected field for a single session. Hand that to an AI step for a summary and open a task, so whoever picks it up starts with the affected views rather than a hunch.
Rotate and retire playback access
Playback IDs are how stream.mux.com URLs reach a video, so retiring one is how you cut off a link. A workflow can mint a fresh playback ID with Mux: Create Asset Playback ID, swap it into your site, and then delete the old one, after which every URL using it stops working immediately. Put an approval step in front of the delete: there is no undo.
Example: A finished render publishes itself and reports the playback link
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a schedule fires, or an earlier workflow step produces the public URL of a finished video file.
Mux: Create Asset from URL ingests the file. The asset comes back in status preparing.
A loop polls Mux: Get Asset until the status is ready, and a condition branches to an alert if it comes back errored instead.
Mux: Create Asset Playback ID mints a playback ID, and the workflow assembles the stream.mux.com playback URL from it.
Mattering Productivity: a task is updated with the asset ID and the playback URL, so the video's home in Mux is on record next to the work it belongs to.
Mux MCP questions, answered
What is the difference between an asset ID, a playback ID, and an upload ID?
They are separate namespaces that happen to look alike. An asset ID identifies the video itself and is what the asset nodes take. A playback ID is a key on an asset or live stream that goes in stream.mux.com playback URLs; an asset can have several, and deleting one kills its URLs without touching the video. An upload ID identifies a direct upload slot, and once the upload finishes, the created asset's ID appears on it as asset_id. Live stream IDs are a fourth namespace again, and a stream key is yet another value. Every ID field on every node says which one it takes, and when all you have is the ID from a playback URL, Mux: Resolve Playback ID looks up which asset or live stream owns it.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Mux through them. Matter, the assistant built into the platform, uses the same nodes natively.
Can the connector upload a video file for me?
Not the bytes, no, and the nodes are honest about it. Mux: Create Asset from URL ingests a file Mux can fetch from a publicly reachable URL, which covers most pipeline cases. Mux: Create Direct Upload URL creates an upload slot and returns a signed URL; your own client, browser, or script then PUTs the file to that URL, and the node never handles the file itself. If nothing ever sends the file, the upload sits in waiting until Mux times it out.
What credential does the connector need, and how do Mux environments affect it?
A Mux access token, sent as HTTP Basic auth with the Token ID as the username and the Token Secret as the password. You create it in the Mux dashboard under Settings, then Access Tokens. Tokens are scoped to a single Mux environment, so a token from your development environment cannot see production assets: if a node returns an empty list while the dashboard shows videos, check which environment the token belongs to. The Token Secret is shown once at creation, so store it in the credential right away.
Will running these nodes cost money on my Mux account?
It can. Mux bills on usage: creating an asset spends encoding, keeping it spends storage, and playback and live streaming spend delivery, so the nodes that create assets and run live streams note that they are billable. Mux's test mode is the safe rehearsal space: pass the test flag when creating assets, live streams, or uploads and Mux produces free, watermarked objects, capped at ten seconds and deleted automatically after 24 hours. Check Mux's own pricing page for current rates; this page does not quote them.
Can an AI agent run a live stream end to end?
Yes. Mux: Create Live Stream returns the stream key and a playback ID, Mux: Enable Live Stream and Mux: Disable Live Stream control whether the encoder can connect, Mux: Signal Live Stream Complete closes out playback when the broadcast is over, and Mux: Update Live Stream adjusts settings like latency mode and the reconnect window. Treat Mux: Reset Stream Key with care: the old key stops working the moment the node runs, which is exactly what you want after a leak and exactly what you do not want mid-broadcast.
Why do the analytics nodes fail or come back empty when the video nodes work?
Two separate causes. Mux access tokens carry separate permissions for Mux Video and Mux Data, so a token created without Mux Data permission fails on the analytics nodes while the video nodes keep working; create a new token with both permissions to fix it. Empty results are different: Mux Data collects from real player sessions, so a fresh account or an environment with no player traffic returns empty result sets with a successful status. That is Mux telling you there were no views, not a broken credential.
Which operations are destructive, and what does the connector not cover?
Five nodes deserve care. Mux: Delete Asset permanently removes the video, Mux: Delete Live Stream removes the stream (already-recorded assets survive), the asset and live stream playback ID deletes kill every URL using that playback ID immediately, and Mux: Reset Stream Key invalidates the old key the instant it runs. Put approval steps in front of them in workflows that run unattended. Not covered in this first version: binary downloads of master files or MP4 renditions, DRM, signing keys for signed playback, simulcast targets, and Mux spaces.
Put Mux to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Mux is a product of its respective owner; Mattering is an independent platform.