How do I create a Mux API Token?

Go to the Mux Dashboard, navigate to Settings > API Tokens, and click 'Create new token'. Ensure you copy the Token Secret immediately as it will only be shown once.

What format should the asset URL be?

The URL must be publicly accessible and point directly to a video file (e.g., MP4, MOV). Mux will then fetch and process the file from that location.

Is the analytics data real-time?

Yes, the `get_recent_views` tool retrieves near real-time data about video views occurring in your account.

Mux MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Name: Mux
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 11 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Mux and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Mux MCP Server

Connect your Mux Video account to your AI agent and take full control of your video infrastructure and streaming workflows through natural conversation.

GitHub Copilot Agent mode brings Mux data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Asset Management — List all video assets and get real-time status updates, durations, and playback IDs.
Asset Creation — Create new video assets instantly by providing a public URL to your source file.
Live Streaming — Access and monitor your live stream configurations and their current status.
Direct Uploads — Create secure upload sessions for uploading video files directly.
Video Analytics — Get recent video view metrics to track your content's reach.
Deep Inspection — Fetch complete metadata for specific assets or live streams using their unique IDs.

The Mux MCP Server exposes 11 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Mux to VS Code Copilot via MCP

Follow these steps to integrate the Mux MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Mux

Ask Copilot: "Using Mux, help me...". 11 tools available

Why Use VS Code Copilot with the Mux MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Mux through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Mux + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Mux MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Mux MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect Mux to VS Code Copilot via MCP:

create_asset

Create a new video asset

create_direct_upload

Create a direct upload session

create_live_stream

Create a new live stream

delete_asset

Delete a video asset

delete_live_stream

Delete a live stream

get_asset

Get specific asset details

get_live_stream

Get specific live stream details

get_recent_views

Get recent video views analytics

list_assets

List Mux video assets

list_direct_uploads

List direct video uploads

list_live_streams

List Mux live streams

Example Prompts for Mux in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Mux immediately.

"List all my video assets and show their status."

"Create a new video asset from https://example.com/video.mp4."

"Check recent views for my videos."

Troubleshooting Mux MCP Server with VS Code Copilot

Common issues when connecting Mux to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Mux + VS Code Copilot FAQ

Common questions about integrating Mux MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.