# Mux TypeScript API Library [Official] [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/muxinc/mux-node-sdk  
**GitHub Stars:** 182  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-116

## Description
Official Mux API wrapper for Node projects, supporting both Mux Data and Mux Video.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Mux TypeScript API Library does

The Mux TypeScript API Library MCP server gives AI assistants an MCP interface to the Mux REST API and its Node.js SDK. It is intended for developers working with Mux Data and Mux Video from server-side TypeScript or JavaScript applications.

Agents can use the server to inspect API endpoints, try requests, and refer to SDK documentation while planning or implementing an integration. This makes it useful for checking how an API operation is represented in the SDK before adding equivalent code to an application.

The underlying library is the official `@mux/ts` package. Outside MCP usage, that package provides typed request parameters and response fields, Mux API client methods, JWT helpers, and webhook utilities.

## How it works

The Mux TypeScript API Library MCP server is launched as an npm package with `npx`. An MCP-compatible client starts the process and passes the configured environment variables to it. The assistant can then interact with the exposed Mux API documentation and request capabilities through MCP.

Mux authentication and signing settings are provided as environment variables rather than embedded in prompts or source files. The available configuration covers API credentials, webhook verification, JWT signing, and an authorization token. The exact variables needed depend on the Mux operation being used.

Requests made through the server should be treated as interactions with the Mux REST API. Developers should review the relevant Mux API documentation and consider the effects of any request that changes account or media state.

## Setup and configuration

Configure the MCP client to run:

```sh
npx -y @mux/mcp
```

Set the credentials required by the operations you intend to use.

- `MUX_TOKEN_ID`
- `MUX_TOKEN_SECRET`
- `MUX_WEBHOOK_SECRET`
- `MUX_SIGNING_KEY`
- `MUX_PRIVATE_KEY`
- `MUX_AUTHORIZATION_TOKEN`

Cursor and VS Code installation links are provided in the project README. MCP clients may require environment variables to be entered in their own configuration interface.

## Tools and capabilities

The Mux TypeScript API Library MCP server supports the following documented workflows:

- Explore Mux API endpoints.
- Make test requests against the API.
- Use SDK documentation when integrating the library.
- Work with both Mux Data and Mux Video API areas.
- Help investigate the `@mux/ts` client’s typed methods, request parameters, and response fields.

The underlying SDK also documents related application capabilities, including creating video assets, signing playback and viewer-count JWTs, and validating and parsing webhook payloads.

## Limitations and notes

It also does not state which credentials are mandatory for every operation. Configure only the variables relevant to the API features your client needs, and verify behavior against the Mux REST API documentation.

The package is designed for server-side TypeScript or JavaScript. SDK version 14 changed internal workings, so integrations upgrading from an earlier version should consult the project’s migration guidance.

_Full upstream README: https://allmcps.com/mcp/mcp-116/readme_