Compatible with every major AI agent and IDE
What is the Kapwing MCP Server?
Connect your Kapwing account to any AI agent to automate your video production and media rendering workflows through natural conversation.
What you can do
- Automated Rendering — Initiate complex video or image renders using project JSON definitions including layers, text, and dimensions
- Status Tracking — Monitor the real-time progress of your renders and retrieve download URLs once processing is complete
- Asset Management — List and browse all renders associated with your account to keep track of your media history
- Webhook Integration — Optionally receive notifications at a specific URL when your media is ready
How it works
- Subscribe to this server
- Enter your Kapwing API Key
- Start generating and managing media from Claude, Cursor, or any MCP-compatible client
No more manual editing for repetitive tasks. Your AI acts as a video engineer, handling the rendering pipeline for you.
Who is this for?
- Content Creators — automate the generation of repetitive video formats or social media assets
- Developers — integrate video rendering capabilities into your apps without leaving your coding environment
- Marketing Teams — scale content production by generating localized or personalized videos from templates
Built-in capabilities (3)
The project definition includes width, height, and layers (video, text, etc.). Initiates the rendering process for a project
) and download URL for a specific render ID. Retrieves the current status of a render
Returns a list of all renders associated with your account
Why Cursor?
Cursor's Agent mode turns Kapwing into an in-editor superpower. Ask Cursor to generate code using live data from Kapwing and it fetches, processes, and writes. all in a single agentic loop. 3 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
Kapwing in Cursor
Kapwing and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Kapwing 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 | 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 Kapwing in Cursor
The Kapwing 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 3 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
Kapwing for Cursor
Every tool call from Cursor to the Kapwing MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I check if my video render is finished?
You can use the get_render_status tool by providing your unique Render ID. The agent will return the current status (e.g., 'completed') and the download URL if it's ready.
Can I start a new render using a JSON project definition?
Yes! Use the create_render action. You just need to provide the project object containing dimensions and layers. You can also specify a webhookUrl for automated notifications.
Is it possible to see a history of all my renders?
Absolutely. The list_renders tool fetches all renders associated with your authenticated account, allowing the AI to summarize or find specific past projects.
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.
Explore More MCP Servers
View all →
Northflank (Developer Cloud & Orchestration)
10 toolsManage cloud infrastructure via Northflank — deploy microservices, trigger CI builds, and audit background jobs.

Peerbie
16 toolsOrchestrate your entire team's workspace, from Kanban boards to calendar events, completely driven by AI.

Onboard.io Implementation
10 toolsAutomate and manage customer onboarding via Onboard.io — track launch plans, tasks, and progress directly from your AI agent.

Actionstep
8 toolsRun your law practice smarter with case management, document tracking, and client billing all connected to your AI workflow.
