# Mux MCP server

> Manage Mux video assets, live streams, playback IDs and Mux Data by running code against the Mux TypeScript SDK.

- Listing: https://mcp.tc/i/mux
- Connect: use the server's own URL `https://mcp.mux.com` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: Mux
- Homepage: <https://www.mux.com/docs/integrations/mcp-server>
- Repository: <https://github.com/muxinc/mux-ts>
- Package: npm `@mux/mcp`

## About

Connects an AI assistant to the Mux API. It can upload and manage video assets, manage live streams and playback IDs, and query Mux Data. The server uses a Code Mode design: it exposes a documentation search tool and a code tool, and the agent writes TypeScript against the Mux SDK, which runs in an isolated sandbox without web or filesystem access.

Runs as a hosted Streamable HTTP endpoint at https://mcp.mux.com with OAuth sign-in. HTTP Basic auth with a Mux access token ID and secret in the Authorization header is also accepted. A local alternative runs with npx -y @mux/mcp and the MUX\_TOKEN\_ID and MUX\_TOKEN\_SECRET environment variables.

## What it can do

- Upload and manage Mux video assets
- Manage live streams
- Work with playback IDs, including signed playback
- Query Mux Data video analytics
- Search Mux API and SDK documentation
- Run TypeScript against the Mux SDK in a sandbox

## Example prompts

- "List my most recent Mux video assets"
- "Create a new Mux live stream and show me the stream key"
- "Add a public playback ID to this Mux asset"
- "Show Mux Data views for the last 24 hours"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http mux https://mcp.mux.com
```

2. Start Claude Code, type `/mcp`, pick **mux** and choose **Authenticate**. A browser window opens for the Mux sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Mux** and paste this URL:

```url
https://mcp.mux.com
```

3. Click **Add**, then **Connect**, and sign in when Mux asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Mux&connectorUrl=https%3A%2F%2Fmcp.mux.com>) (opens connector settings)

2. Check that the URL reads `https://mcp.mux.com` and click **Add**.

3. Click **Connect** and sign in when Mux asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.mux.com` as the server URL and choose **OAuth**. ChatGPT sends you to Mux to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=mux&config=eyJ1cmwiOiJodHRwczovL21jcC5tdXguY29tIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "mux": {
      "url": "https://mcp.mux.com"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=mux&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.mux.com%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"mux","type":"http","url":"https://mcp.mux.com"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "mux": {
      "type": "http",
      "url": "https://mcp.mux.com"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "mux": {
      "serverUrl": "https://mcp.mux.com"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add mux --url https://mcp.mux.com
codex mcp login mux
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.mux]
url = "https://mcp.mux.com"
```

### Gemini CLI

```bash
gemini mcp add --transport http mux https://mcp.mux.com
```

Then, inside Gemini CLI, run `/mcp auth mux` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "mux": {
      "type": "http",
      "url": "https://mcp.mux.com"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.mux.com`.

## Details

- Server version: 12.8.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/mux (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report