Mux MCP

Live

OAUTH 2.1

VIDEO INFRASTRUCTURE

Developer Tools

Mux MCP gives agents authenticated access to your video infrastructure: search Mux SDK docs and execute sandboxed code against the Mux API for assets, streams, and playback.

  • Per-user credentials: each call uses the actual user's token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Mux MCP
agent · Acme Q3
Run
How many views did asset abc123 get in the last 7 days?
S
muxmcp_execute
156ms
Mux agent
Asset abc123 had 4,210 views in the last 7 days, 92% completion rate.
Sources: 1 asset, 7-day window
muxmcp
1 asset
18:29
Message Claude...

Tools your video agent reaches for on Mux, scoped per user.

CALL ANY TOOL
Query video infrastructure end to end: search SDK docs, then execute sandboxed code against the Mux API.
muxmcp_search_docs
Search docs
Search SDK documentation to find methods, parameters, and usage examples for interacting with the Mux API.
Parameters
Name
Type
Required
Description
language
string
Required
The language for the SDK to search for.
query
string
Required
The query to search for.
detail
string
Optional
The amount of detail to return.
muxmcp_execute
Execute
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Mux tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["muxmcp"], toolNames: [
    "muxmcp_search_docs",
    "muxmcp_execute",
    "muxmcp_search_docs"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "How many views did asset abc123 get in the last 7 days?" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["muxmcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "How many views did asset abc123 get in the last 7 days?" }],
  tools,
});

// Execute the tool call with the user's vaulted muxmcp credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["muxmcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "How many views did asset abc123 get in the last 7 days?" }],
  tools,
});

// Tool call runs with the user's vaulted muxmcp credential
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["muxmcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "muxmcp_agent",
  model: "gemini-2.5-pro",
  instruction: "Mux tools scoped to this user",
  tools,
});

await agent.run("How many views did asset abc123 get in the last 7 days?");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Mux MCP tool. Click to copy, paste into your agent, done.
Explore the API
Copy the prompt
Copied
Search Mux docs for how to create a live stream.
Copy the prompt
Copied
Search Mux docs for signed URL playback examples.
Copy the prompt
Copied
Find the method for listing assets by status.
Query video data
Copy the prompt
Copied
How many views did asset abc123 get in the last 7 days?
Copy the prompt
Copied
List all assets created in the last 24 hours.
Copy the prompt
Copied
Get the playback stats for live stream ls_882.
Manage assets
Copy the prompt
Copied
Create a new asset from this input URL.
Copy the prompt
Copied
Delete the asset that failed processing yesterday.
Copy the prompt
Copied
Enable MP4 support on asset abc123.
SEE HOW AUTH WORKS
Your users connect once. Their Mux MCP credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Mux MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Mux MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Mux MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Mux MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other developer-tools and video connectors.
ENGINEERING
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.
01.
Shared tokens break per-user analytics
A shared Mux MCP token looks fine in a demo. In production every API call looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Mux MCP today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Mux MCP as the user or through a shared key?
As the user. Scalekit resolves the credential of the person who triggered the agent at request time, so every Mux MCP action in your audit trail is attributed to a real user, not a shared service account.
Where is the Mux MCP token stored?
In an AES-256 encrypted vault with per-tenant namespacing. Tokens are resolved at request time, never enter LLM context, refresh automatically, and can be revoked from one dashboard.
Can I limit what the agent does in Mux MCP?
Yes. Filter by tool name in listScopedTools to expose only what you want. Scalekit also enforces scope checks before every API call.
What happens when a user revokes access?
The credential is invalidated at the next tool call. The call fails closed, other users' connections are unaffected, and the revocation is logged in the audit chain.
Does the sandboxed code in muxmcp_execute have network access beyond Mux?
No. Code runs in a sandboxed container with no external network access beyond the initialized Mux SDK client, so generated code can only call the Mux API through the credential Scalekit resolves for that user.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""muxmcp"": {
""url"": ""https://mcp.scalekit.com/muxmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.muxmcp]
url = ""https://mcp.scalekit.com/muxmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""muxmcp"": {
""url"": ""https://mcp.scalekit.com/muxmcp"",
""type"": ""http""
}
}
}