Bring Video Hosting
to VS Code Copilot
Learn how to connect Wistia to VS Code Copilot and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Wistia MCP Server?
Connect your Wistia video marketing account to any AI agent to automate your media library management and performance monitoring through natural conversation. Wistia provides a premier platform for B2B video hosting, delivery, and detailed engagement tracking.
What you can do
- Media Orchestration — List and retrieve detailed metadata for your videos (medias), including titles, descriptions, and statuses.
- Project Management — Organize your content by creating and managing hierarchical projects (folders) directly from the AI interface.
- Engagement Analytics — Retrieve real-time performance stats for specific videos or get an aggregated overview of your account-wide metrics.
- Metadata Control — Programmatically update video details and manage captions to ensure your media library is always optimized.
- Asset Delivery — Fetch player configurations and thumbnail URLs to streamline content distribution across your digital channels.
How it works
1. Subscribe to this server
2. Enter your Wistia API Token from your account settings
3. Start managing your video assets from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Marketing Teams — automate the monitoring of video engagement and organize media assets via natural language.
- Video Producers — quickly update video titles and retrieve media links without leaving the project workspace.
- Business Analysts — get instant account-wide video performance reports and visitor metrics straight through the chat.
Built-in capabilities (9)
Create a new project
Get account-wide stats
Get metadata for a project
Get metadata for a video
Get video analytics
List your Wistia projects
List captions for a video
List all videos (medias)
Modify video metadata
Why VS Code Copilot?
GitHub Copilot Agent mode brings Wistia data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 9 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
Wistia in VS Code Copilot
Wistia and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Wistia 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 | 3,400+ 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 Wistia in VS Code Copilot
The Wistia 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 9 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
Wistia for VS Code Copilot
Every tool call from VS Code Copilot to the Wistia MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Wistia API Token?
Log in to Wistia, navigate to Account Settings > API, and generate a new token or copy an existing one from the list.
What is a 'hashed_id'?
A hashed_id is a unique, short identifier assigned to every video and project in Wistia, typically found in the URL when viewing an asset.
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.