Compatible with every major AI agent and IDE
What is the Vidyard MCP Server?
Connect your Vidyard account to any AI agent and manage your business video library through natural conversation.
What you can do
- Video Library — List all video assets stored in your Vidyard dashboard and retrieve unique video IDs
- Metadata & Details — Get technical metadata for any video including length, encoding status, and descriptions
- Player Management — Create, update, and manage video players (facades) to customize how your content is embedded
- Video Organization — Attach videos to specific players and organize your content for different marketing or sales needs
- Direct Stream Access — Retrieve direct stream URLs and raw MP4 download links for various video qualities (480p, 720p, etc.)
- Asset Management — Rename players or permanently delete video assets and player containers from your dashboard
How it works
- Subscribe to this server
- Enter your Vidyard API Token
- Start managing your video library through Claude, Cursor, or any MCP-compatible client
No more manual browsing through complex video dashboards. Your AI agent becomes your video asset manager.
Who is this for?
- Marketing Teams — organize video players for different campaigns and retrieve embed codes through chat
- Sales Professionals — quickly find and share specific videos or product demos with prospects
- Content Creators — manage video assets, check encoding status, and retrieve source files for distribution
- Support Engineers — find relevant tutorial videos and manage player branding for knowledge base articles
Built-in capabilities (10)
Requires both player ID and video ID. Adds a video asset into a specific player container
Creates a new, empty video player container
This action is irreversible. Permanently deletes a video asset from Vidyard
Note that the original video assets are not deleted. Permanently deletes a video player
Retrieves details for a specific video player
Retrieves technical metadata for a specific video asset
Retrieves direct stream URLs for various video qualities (480p, 720p, etc.)
Lists all configured video players (facades) in the account
Lists all video assets stored in the Vidyard dashboard
Updates the display name or title of an existing player
Why VS Code Copilot?
GitHub Copilot Agent mode brings Vidyard data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
Vidyard in VS Code Copilot
Vidyard and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Vidyard to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Vidyard in VS Code Copilot
The Vidyard 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Vidyard for VS Code Copilot
Every tool call from VS Code Copilot to the Vidyard MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I get direct download links for my videos through the agent?
Yes. The get_video_source_files tool allows your agent to retrieve direct MP4 download links and stream URLs for different qualities (like 720p or 1080p), making it easy to share raw files or use them in other applications.
How do I add a video to a specific player?
Use the attach_video_to_player tool. You'll need to provide the player_id and the video_id. Your agent can help you find these IDs by listing your players and videos first.
Can I create new video players through conversation?
Absolutely. The create_empty_player tool lets you provision a new player container with a descriptive name. Once created, you can attach videos to it and manage its settings directly through your agent.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Georef Argentina
7 toolsAccess official Argentine geographic data—normalize addresses, list administrative divisions, and perform reverse geocoding directly from your AI.

Flodesk
12 toolsManage email subscribers, segments, and workflows via AI agents with Flodesk.

YAML Parser Engine
1 toolsConvert YAML to JSON and JSON to YAML with absolute precision — including anchors, aliases, and multi-document support. The engine behind Kubernetes, GitHub Actions, and Docker Compose config processing. 30M+ weekly downloads.

Strava
12 toolsManage activities, athlete stats, and routes on Strava with AI agents.
