api.video MCP Server for Claude DesktopGive Claude Desktop instant access to 9 tools to Create Video Object, Delete Video, Get Video Analytics, and more
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
Ask AI about this App Connector for Claude Desktop
The api.video app connector for Claude Desktop is a standout in the Developer Tools category — giving your AI agent 9 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install api.video and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"apivideo": {
// Your Vinkius token. get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 api.video MCP Server
Connect your api.video account to any AI agent and take full control of your professional video hosting infrastructure and automated media workflows through natural conversation.
Claude Desktop is the definitive way to connect api.video to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
What you can do
- Video Orchestration — List and manage your entire high-fidelity video library programmatically, or create new video objects to prepare for uploads in real-time
- Asset Intelligence — Retrieve detailed high-fidelity status and direct asset URLs for players, thumbnails, and navigation markers (chapters) directly through your agent
- Deep Analytics Tracking — Monitor performance metrics like total plays and impressions using high-fidelity aggregation tools to coordinate your content strategy
- Multilingual Captions — Access and manage subtitle tracks across multiple languages to maintain a perfectly coordinated global viewer experience
- Infrastructure Monitoring — Access your directory of custom player themes and store-level metadata directly through your agent for instant operational reporting
The api.video MCP Server exposes 9 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 9 api.video tools available for Claude Desktop
When Claude Desktop connects to api.video through Vinkius, your AI agent gets direct access to every tool listed below — spanning video-hosting, video-streaming, encoding, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Set title and description here. Initialize a new video
video. Permanently delete a video
Retrieve performance metrics
Get metadata for a video
List custom player themes
List captions for a video
List chapters for a video
Supports filtering by title or tags. List your api.video videos
Modify video metadata
Connect api.video to Claude Desktop via MCP
Follow these steps to wire api.video into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open Claude Desktop Settings
claude_desktop_config.jsonAdd the MCP Server
mcpServers sectionRestart Claude Desktop
Start using api.video
Why Use Claude Desktop with the api.video MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with api.video through the Model Context Protocol.
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
api.video + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the api.video MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
Example Prompts for api.video in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with api.video immediately.
"List the last 5 videos in my api.video account."
"Show the play count analytics for all videos this month."
"Get the player link and captions for video ID 'vi123'."
Troubleshooting api.video MCP Server with Claude Desktop
Common issues when connecting api.video to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
api.video + Claude Desktop FAQ
Common questions about integrating api.video MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.