4,500+ servers built on MCP Fusion
Vinkius
Kapwing logo
Vinkius
Claude Code logo

How to Use the Kapwing MCP in Claude Code

Automate video rendering in your CI/CD pipelines. Pipe JSON to Kapwing directly from the Claude Code terminal.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Kapwing MCP on Cursor AI Code Editor MCP Client Kapwing MCP on Claude Desktop App MCP Integration Kapwing MCP on OpenAI Agents SDK MCP Compatible Kapwing MCP on Visual Studio Code MCP Extension Client Kapwing MCP on GitHub Copilot AI Agent MCP Integration Kapwing MCP on Google Gemini AI MCP Integration Kapwing MCP on Lovable AI Development MCP Client Kapwing MCP on Mistral AI Agents MCP Compatible Kapwing MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Claude Code

Connect Kapwing MCP to Claude Code

Create your Vinkius account to connect Kapwing to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Render Videos from the Command Line

The `create_render` tool takes a JSON payload and starts a Kapwing render job. You can pipe a JSON file directly to it or construct the payload within a shell script. It's built for headless automation. For example, you can set up a GitHub Action that generates a JSON file, then uses Claude Code to call `create_render`. The action gets back a render ID, which you can pass to the next step in your pipeline.

Script Your Render Status Checks

Use `get_render_status` with a render ID to poll for completion. The tool outputs the status and, once finished, the download URL. This is essential for any script that needs to wait for a video before continuing. Write a simple bash script that calls `create_render`, then loops and calls `get_render_status` every 10 seconds. Once the status is 'complete', the script can use `curl` to download the file and move on. Claude Code makes this trivial.

Manage Assets with this Claude Code MCP Server

The `list_renders` tool dumps a JSON array of all your previous renders. You can pipe this output to tools like `jq` to filter, search, and process your asset history right in the terminal. Set up a nightly cron job that runs `claude mcp call kapwing-mcp list_renders`, pipes the output to a script that checks for old or failed renders, and sends a notification. It's simple, reliable, and requires no UI.

Setup guide

Set up Kapwing MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see kapwing-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest Kapwing transactions." It will automatically discover and invoke the available Kapwing tools.

Terminal
claude mcp add --transport http kapwing-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Kapwing MCP in Claude Code

In your workflow YAML, install Claude Code, add the Kapwing server, and then call the tools. For example, `claude mcp call kapwing-mcp create_render < project.json` to start a job, and then poll with `get_render_status`.
Absolutely. You can store the render ID from `create_render` in a shell variable, then pass that variable to `get_render_status` inside a loop. This is a common pattern for automating render-and-download tasks.
Pipe it. Generate your JSON with another tool or script and pipe it into `claude mcp call kapwing-mcp create_render`. For parsing output from `list_renders` or `get_render_status`, pipe the result to `jq`.
It's a single command: `claude mcp add --transport http kapwing-mcp -- `. After that, the tools are available immediately. Your config is saved in `~/.claude.json`.
Only the JSON project data for each render is sent through the MCP server to Kapwing's API. The connection is secured by your Vinkius token, and the server itself doesn't log or persist your project's content.

Start using the Kapwing MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 3 tools

We've already built the connector for Kapwing. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.