by Mux
Updated October 19, 2026
MCP100 verdict
Not currently recommended. Shortlist — editorially admitted, not a Recommended endorsement.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Restrict methods or use read-only GET mode; authenticated tool test unavailable
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Evidence scope
182 shared-repository stars · not MCP-specific
3.4k package downloads / 30 days
Repository identity: muxinc/mux-ts
Package identity: @mux/mcp · version 15.6.1
Stars observed October 20, 2026 · Downloads observed October 20, 2026
The official `@mux/mcp` server package lives inside the broader `muxinc/mux-ts` monorepo. The repository star count is therefore shared with the Mux TypeScript SDK and is not MCP-specific.
Exact MCP-specific npm package; 30-day downloads are directly attributable to this MCP package.
Publisher activity observed October 19, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-19
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
{"url":"https://mcp.mux.com"}Capability
Mux MCP is a Mux MCP integration for video api operations, livestreams and analytics. Useful for teams already operating Mux video infrastructure. No Mux account or auth for anonymous access; broad execute tool can mutate resources.
Search Mux API and SDK documentation
Run Mux TypeScript SDK operations within the authorized environment
Hosted Code Mode exposes two MCP tools; execute dynamically reaches far more Mux SDK operations
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://mcp.mux.com
Reviewed access
Related reviewed MCPs
Let AI clients inspect and automate web browsers with Playwright.
Choose this instead if
Choose Playwright MCP instead if inspecting and testing web interfaces through accessibility snapshots.
Let AI clients inspect and automate web browsers with Playwright.
Search Hugging Face Hub resources and use explicitly enabled Jobs, sandboxes, and community Space tools.
Choose this instead if
Choose Hugging Face MCP instead if searching models, datasets, Spaces, papers, and Hugging Face documentation.
Search Hugging Face Hub resources and use explicitly enabled Jobs, sandboxes, and community Space tools.
Read and manage Asana workspaces, tasks, projects, portfolios, and reports.
Choose this instead if
Choose Asana MCP instead if read and manage Asana workspaces, tasks, projects, portfolios, and reports.
Read and manage Asana workspaces, tasks, projects, portfolios, and reports.
Mux is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
npm install @mux/ts
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
This library provides convenient access to the Mux REST API from server-side TypeScript or JavaScript.
The REST API documentation can be found on docs.mux.com. The full API of this library can be found in api.md.
Note: As of v14 of mux-node-sdk, we have changed some internal workings of the SDKs. You can read more about this here.
Use the Mux MCP Server to enable AI assistants to interact with this API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.
Note: You may need to set environment variables in your MCP client.
The full API of this library can be found in api.md.
import Mux from '@mux/ts';
const client = new Mux({
tokenId: process.env['MUX_TOKEN_ID'], // This is the default and can be omitted
tokenSecret: process.env['MUX_TOKEN_SECRET'], // This is the default and can be omitted
});
const asset = await client.video.assets.create({
inputs: [{ url: 'https://storage.googleapis.com/muxdemofiles/mux-video-intro.mp4' }],
playback_policies: ['public'],
});
console.log(asset.id);
This library includes TypeScript definitions for all request params and response fields. You may import and use them like so:
import Mux from '@mux/ts';
const client = new Mux({
tokenId: process.env['MUX_TOKEN_ID'], // This is the default and can be omitted
tokenSecret: process.env['MUX_TOKEN_SECRET'], // This is the default and can be omitted
});
const params: Mux.Video.AssetCreateParams = {
inputs: [{ url: 'https://storage.googleapis.com/muxdemofiles/mux-video-intro.mp4' }],
playback_policies: ['public'],
};
const asset: Mux.Video.Asset = await client.video.assets.create(params);
Documentation for each method, request param, and response field are available in docstrings and will appear on hover in most modern editors.
You can use any JWT-compatible library, but we've included some light helpers in the SDK to make it easier to get up and running.
// Assuming you have your signing key specified in your environment variables:
// Signing token ID: process.env.MUX_SIGNING_KEY
// Signing token secret: process.env.MUX_PRIVATE_KEY
// Most simple request, defaults to type video and is valid for 7 days.
const token = mux.jwt.signPlaybackId('some-playback-id');
// https://stream.mux.com/some-playback-id.m3u8?token=${token}
// If you wanted to sign a thumbnail
const thumbParams = { time: 14, width: 100 };
const thumbToken = mux.jwt.signPlaybackId('some-playback-id', {
type: 'thumbnail',
params: thumbParams,
});
// https://image.mux.com/some-playback-id/thumbnail.jpg?token=${token}
// If you wanted to sign a gif
const gifToken = mux.jwt.signPlaybackId('some-playback-id', { type: 'gif' });
// https://image.mux.com/some-playback-id/animated.gif?token=${token}
// Here's an example for a storyboard
const storyboardToken = mux.jwt.signPlaybackId('some-playback-id', {
type: 'storyboard',
});
// https://image.mux.com/some-playback-id/storyboard.jpg?token=${token}
// You can also use `signViewerCounts` to get a token
// used for requests to the Mux Engagement Counts API
// https://docs.mux.com/guides/see-how-many-people-are-watching
const statsToken = mux.jwt.signViewerCounts('some-live-stream-id', {
type: 'live_stream',
});
// https://stats.mux.com/counts?token={statsToken}
In cases you need multiple tokens, like when using Mux Player, things can get unwieldy pretty quickly. For example,
const playbackToken = await mux.jwt.signPlaybackId(id, {
expiration: "1d",
type: "playback"
})
const thumbnailToken = await mux.jwt.signPlaybackId(id, {
expiration: "1d",
type: "thumbnail",
})
const storyboardToken = await mux.jwt.signPlaybackId(id, {
expiration: "1d",
type: "storyboard"
})
const drmToken = await mux.jwt.signPlaybackId(id, {
expiration: "1d",
type: "drm_license"
})
<mux-player
playback-token={playbackToken}
thumbanil-token={thumbnailToken}
storyboard-token={storyboardToken}
drm-token={drmToken}
playbackId={id}
></mux-player>
To simplify this use-case, you can provide multiple types to signPlaybackId to recieve multiple tokens. These tokens are provided in a format that Mux Player can take as props:
// { "playback-token", "thumbnail-token", "storyboard-token", "drm-token" }
const tokens = await mux.jwt.signPlaybackId(id, {
expiration: "1d",
type: ["playback", "thumbnail", "storyboard", "drm_license"]
})
<mux-player
{...tokens}
playbackId={id}
></mux-player>
If you would like to provide params to a single token (e.g., if you would like to have a thumbnail time), you can provide [type, typeParams] instead of type:
const tokens = await mux.jwt.signPlaybackId(id, {
expiration: '1d',
type: ['playback', ['thumbnail', { time: 2 }], 'storyboard', 'drm_license'],
});
To validate that the given payload was sent by Mux and parse the webhook payload for use in your application,
you can use the mux.webhooks.unwrap utility method.
This method accepts a raw body string and a list of headers. As long as you have set your webhookSecret in the
appropriate configuration property when instantiating the library, all webhooks will be verified for authenticity automatically.
The following example shows how you can handle a webhook using a Next.js app directory API route:
// app/api/mux/webhooks/route.ts
import { revalidatePath } from 'next/cache';
import { headers } from 'next/headers';
import Mux from '@mux/ts';
const mux = new Mux({
webhookSecret: process.env.MUX_WEBHOOK_SECRET,
});
export async function POST(request: Request) {
const headersList = headers();
const body = await request.text();
const event = await mux.webhooks.unwrap(body, headersList);
switch (event.type) {
case 'video.live_stream.active':
case 'video.live_stream.idle':
case 'video.live_stream.disabled':
/**
* `event` is now understood to be one of the following types:
*
* | Mux.Webhooks.VideoLiveStreamActiveWebhookEvent
* | Mux.Webhooks.VideoLiveStreamIdleWebhookEvent
* | Mux.Webhooks.VideoLiveStreamDisabledWebhookEvent
*/
if (event.data.id === 'MySpecialTVLiveStreamID') {
revalidatePath('/tv');
}
break;
default:
break;
}
return Response.json({ message: 'ok' });
}
Verifying Webhook Signatures is optional but encouraged. Learn more in our Webhook Security Guide
/*
If the header is valid, this function will not throw an error and will not return a value.
If the header is invalid, this function will throw one of the following errors:
- new Error(
"The webhook secret must either be set using the env var, MUX_WEBHOOK_SECRET, on the client class, Mux({ webhookSecret: '123' }), or passed to this function",
);
- new Error('Could not find a mux-signature header');
- new Error(
'Webhook body must be the raw request body (string or bytes), not parsed JSON.',
);
- new Error('Unable to extract timestamp and signatures from header')
- new Error('No v1 signatures found');
- new Error('No signatures found matching the expected signature for payload.')
- new Error('Webhook timestamp is too old')
*/
/*
`body` is the raw request body, as a string or bytes (Buffer, Uint8Array, ArrayBuffer).
`headers` is the value in request.headers
`secret` is the signing secret for this configured webhook. You can find that in your webhooks dashboard
(note that this secret is different than your API Secret Key)
*/
mux.webhooks.verifySignature(body, headers, secret);
Note that when passing in the payload (body) you want to pass in the raw un-parsed request body, not the parsed JSON. Here's an example if you are using express.
const Mux = require('@mux/ts');
const mux = new Mux();
const express = require('express');
const bodyParser = require('body-parser');
/**
* You'll need to make sure this is externally accessible. ngrok (https://ngrok.com/)
* makes this really easy.
*/
const webhookSecret = process.env.WEBHOOK_SECRET;
const app = express();
app.post('/webhooks', bodyParser.raw({ type: 'application/json' }), async (req, res) => {
try {
// will raise an exception if the signature is invalid
const isValidSignature = await mux.webhooks.verifySignature(req.body, req.headers, webhookSecret);
console.log('Success:', isValidSignature);
// convert the raw req.body to JSON, which is originally Buffer (raw)
const jsonFormattedBody = JSON.parse(req.body);
// await doSomething();
res.json({ received: true });
} catch (err) {
// On error, return the error message
return res.status(400).send(`Webhook Error: ${err.message}`);
}
});
app.listen(3000, () => {
console.log('Example app listening on port 3000!');
});
When the library is unable to connect to the API,
or if the API returns a non-success status code (i.e., 4xx or 5xx response),
a subclass of APIError will be thrown:
const liveStream = await client.video.liveStreams
.create({ playback_policies: ['public'] })
.catch(async (err) => {
if (err instanceof Mux.APIError) {
console.log(err.status); // 400
console.log(err.name); // BadRequestError
console.log(err.headers); // {server: 'nginx', ...}
} else {
throw err;
}
});
Error codes are as follows:
| Status Code | Error Type |
|---|---|
| 400 | BadRequestError |
| 401 | AuthenticationError |
| 403 | PermissionDeniedError |
| 404 | NotFoundError |
| 422 | UnprocessableEntityError |
| 429 | RateLimitError |
| >=500 | InternalServerError |
| N/A | APIConnectionError |
Certain errors will be automatically retried 2 times by default, with a short exponential backoff. Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict, 429 Rate Limit, and >=500 Internal errors will all be retried by default.
You can use the maxRetries option to configure or disable this:
// Configure the default for all requests:
const client = new Mux({
maxRetries: 0, // default is 2
});
// Or, configure per-request:
await client.video.assets.retrieve('t02rm...', {
maxRetries: 5,
});
Requests time out after 1 minute by default. You can configure this with a timeout option:
// Configure the default for all requests:
const client = new Mux({
timeout: 20 * 1000, // 20 seconds (default is 1 minute)
});
// Override per-request:
await client.video.assets.retrieve('t02rm...', {
timeout: 5 * 1000,
});
On timeout, an APIConnectionTimeoutError is thrown.
Note that requests which time out will be retried twice by default.
List methods in the Mux API are paginated.
You can use the for await … of syntax to iterate through items across all pages:
async function fetchAllDeliveryReports(params) {
const allDeliveryReports = [];
// Automatically fetches more pages as needed.
for await (const deliveryReport of client.video.deliveryUsage.list()) {
allDeliveryReports.push(deliveryReport);
}
return allDeliveryReports;
}
Alternatively, you can request a single page at a time:
let page = await client.video.deliveryUsage.list();
for (const deliveryReport of page.data) {
console.log(deliveryReport);
}
// Convenience methods are provided for manually paginating:
while (page.hasNextPage()) {
page = await page.getNextPage();
// ...
}
The "raw" Response returned by fetch() can be accessed through the .asResponse() method on the APIPromise type that all methods return.
This method returns as soon as the headers for a successful response are received and does not consume the response body, so you are free to write custom parsing or streaming logic.
You can also use the .withResponse() method to get the raw Response along with the parsed data.
Unlike .asResponse() this method consumes the body, returning once it is parsed.
const client = new Mux();
const response = await client.video.assets
.create({
inputs: [{ url: 'https://storage.googleapis.com/muxdemofiles/mux-video-intro.mp4' }],
playback_policies: ['public'],
})
.asResponse();
console.log(response.headers.get('X-My-Header'));
console.log(response.statusText); // access the underlying Response object
const { data: asset, response: raw } = await client.video.assets
.create({
inputs: [{ url: 'https://storage.googleapis.com/muxdemofiles/mux-video-intro.mp4' }],
playback_policies: ['public'],
})
.withResponse();
console.log(raw.headers.get('X-My-Header'));
console.log(asset.id);
[!IMPORTANT] All log messages are intended for debugging only. The format and content of log messages may change between releases.
The log level can be configured in two ways:
MUX_LOG environment variablelogLevel client option (overrides the environment variable if set)import Mux from '@mux/ts';
const client = new Mux({
logLevel: 'debug', // Show all log messages
});
Available log levels, from most to least verbose:
'debug' - Show debug messages, info, warnings, and errors'info' - Show info messages, warnings, and errors'warn' - Show warnings and errors (default)'error' - Show only errors'off' - Disable all loggingAt the 'debug' level, all HTTP requests and responses are logged, including headers and bodies.
Some authentication-related headers are redacted, but sensitive data in request and response bodies
may still be visible.
By default, this library logs to globalThis.console. You can also provide a custom logger.
Most logging libraries are supported, including pino, winston, bunyan, consola, signale, and @std/log. If your logger doesn't work, please open an issue.
When providing a custom logger, the logLevel option still controls which messages are emitted, messages
below the configured level will not be sent to your logger.
import Mux from '@mux/ts';
import pino from 'pino';
const logger = pino();
const client = new Mux({
logger: logger.child({ name: 'Mux' }),
logLevel: 'debug', // Send all messages to pino, allowing it to filter
});
This library is typed for convenient access to the documented API. If you need to access undocumented endpoints, params, or response properties, the library can still be used.
To make requests to undocumented endpoints, you can use client.get, client.post, and other HTTP verbs.
Options on the client, such as retries, will be respected when making these requests.
await client.post('/some/path', {
body: { some_prop: 'foo' },
query: { some_query_arg: 'bar' },
});
To make requests using undocumented parameters, you may use // @ts-expect-error on the undocumented
parameter. This library doesn't validate at runtime that the request matches the type, so any extra values you
send will be sent as-is.
client.video.assets.create({
// ...
// @ts-expect-error baz is not yet public
baz: 'undocumented option',
});
For requests with the GET verb, any extra params will be in the query, all other requests will send the
extra param in the body.
If you want to explicitly send an extra argument, you can do so with the query, body, and headers request
options.
To access undocumented response properties, you may access the response object with // @ts-expect-error on
the response object, or cast the response object to the requisite type. Like the request params, we do not
validate or strip extra properties from the response from the API.
By default, this library expects a global fetch function is defined.
If you want to use a different fetch function, you can either polyfill the global:
import fetch from 'my-fetch';
globalThis.fetch = fetch;
Or pass it to the client:
import Mux from '@mux/ts';
import fetch from 'my-fetch';
const client = new Mux({ fetch });
If you want to set custom fetch options without overriding the fetch function, you can provide a fetchOptions object when instantiating the client or making a request. (Request-specific options override client options.)
import Mux from '@mux/ts';
const client = new Mux({
fetchOptions: {
// `RequestInit` options
},
});
To modify proxy behavior, you can provide custom fetchOptions that add runtime-specific proxy
options to requests:
Node [docs]
import Mux from '@mux/ts';
import * as undici from 'undici';
const proxyAgent = new undici.ProxyAgent('http://localhost:8888');
const client = new Mux({
fetchOptions: {
dispatcher: proxyAgent,
},
});
Bun [docs]
import Mux from '@mux/ts';
const client = new Mux({
fetchOptions: {
proxy: 'http://localhost:8888',
},
});
Deno [docs]
import Mux from 'npm:@mux/ts';
const httpClient = Deno.createHttpClient({ proxy: { url: 'http://localhost:8888' } });
const client = new Mux({
fetchOptions: {
client: httpClient,
},
});
This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:
We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.
We are keen for your feedback; please open an issue with questions, bugs, or suggestions.
TypeScript >= 4.9 is supported.
The following runtimes are supported:
"node" environment ("jsdom" is not supported at this time).Note that React Native is not supported at this time.
If you are interested in other runtime environments, please open or upvote an issue on GitHub.