How to Use the Mux MCP in VS Code Copilot

Q: How do we deploy Mux to our VS Code Copilot users?

Commit a .vscode/mcp.json file to your Git repository with the Mux server details. Every developer pulling that repo automatically gets the tools in their editor.

Share video infrastructure tools across your entire engineering team via MCP in VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Mux MCP to VS Code Copilot

Create your Vinkius account to connect Mux to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Mux with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-Wide Asset Management in VS Code

The Mux MCP Server allows your entire development team to manage video storage directly from VS Code. A developer asks Copilot to initialize a new media record, and the agent runs `create_asset` to return the playback credentials. Because the configuration lives in your repository, every engineer has immediate access to these same commands. Frontend teams can bypass backend bottlenecks by asking Copilot for upload endpoints. The agent executes `create_direct_upload` and hands over the secure URL. When QA needs to verify the pipeline, they prompt Copilot to run `list_assets` and `get_asset` to confirm the files processed correctly.

Standardize Live Stream Testing

Large streaming applications need predictable test environments. Copilot standardizes this by using `create_live_stream` to generate temporary RTMP endpoints for local testing. Any engineer on the team can spin up a broadcast target without needing separate dashboard credentials. During load testing, developers monitor the ingest status directly in their editor. Copilot calls `get_live_stream` to check connection health and `list_live_streams` to audit active sessions. When testing concludes, the agent runs `delete_live_stream` to enforce clean infrastructure practices.

Debug Playback Metrics Inline

Building data pipelines requires understanding the exact shape of your media metrics. Copilot pulls this data by executing `get_recent_views` right inside the editor chat. Your data engineers see the exact JSON schema for video performance before writing a single line of parsing logic. If an engineer spots an anomaly in the view counts, they investigate it immediately. They tell their AI client to run `get_asset` on the flagged video ID. The agent retrieves the specific encoding details, helping the team debug playback issues without leaving their IDE.

Setup guide

Set up Mux MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Mux MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Mux tools listed. Try asking: "List my recent Mux transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "mux-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mux. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Mux now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Mux MCP in VS Code Copilot

Commit a `.vscode/mcp.json` file to your Git repository with the Mux server details. Every developer pulling that repo automatically gets the tools in their editor.

Yes. Any authorized developer can ask the agent to provision a stream. It returns the RTMP URL and stream key for immediate use in local environments.

The agent will execute the delete tool and remove the video. You should provision a specific staging token for this integration to prevent accidental production deletion.

It provides direct access to recent analytics. Developers can pull viewer metrics to understand the data structure before building reporting dashboards.

Vinkius handles your video IDs, stream configurations, and playback analytics through ephemeral sandboxes. Copilot accesses your media pipeline via a single endpoint token, ensuring no raw credentials sit on local developer machines.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript