Bring Video Hosting
to Cursor
Learn how to connect api.video to Cursor 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 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.
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
How it works
1. Subscribe to this server
2. Retrieve your Production API Key from your api.video dashboard (API Keys section)
3. Start orchestrating your video content and performance from Claude, Cursor, or any MCP client
No more manual toggling between video dashboards or digging through complex embed settings. Your AI acts as your dedicated video engineer and media architect.
Who is this for?
- Content Creators — instantly retrieve player links and update video metadata using natural language commands
- Product Managers — monitor video performance and track feature walkthrough engagement without leaving your creative workspace
- Developers — integrate high-speed cloud-based video management into custom application workflows through simple AI queries
Built-in capabilities (9)
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
Why Cursor?
Cursor's Agent mode turns api.video into an in-editor superpower. Ask Cursor to generate code using live data from api.video and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
api.video in Cursor
api.video and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect api.video to Cursor 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 api.video in Cursor
The api.video 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 Cursor 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
api.video for Cursor
Every tool call from Cursor to the api.video 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 api.video API Key?
Log in to your account, navigate to the API Keys section in your dashboard, and copy your unique Production API Key.
Can I get a direct player link via AI?
Yes! The get_video_details tool retrieves high-fidelity asset URLs including the player, mp4 source, and thumbnails for any specific video.
How do I check video analytics?
Use the get_video_analytics tool and specify the metric (e.g., 'play') and aggregation (e.g., 'total') to retrieve real-time performance data.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.