How to Use the Kapwing MCP in Cline

Let Cline build video features into your app. It will write the code, call the Kapwing API, and manage the assets.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Kapwing MCP to Cline

Create your Vinkius account to connect Kapwing to Cline 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

Setup Kapwing with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Trigger Renders from Your Codebase

The `create_render` tool is your entry point for generating media. Tell Cline to build a feature that lets users create custom videos, and it will write the code to construct the JSON payload and call this tool. Cline doesn't just call the API; it integrates it. It can create a new file, write a TypeScript function that calls `create_render`, and even stage the commit for you. The entire workflow happens inside your editor.

Build Real-time Status UIs with Cline

Use `get_render_status` to check the progress of a render job and get the final URL. This is the key to building any kind of user-facing progress indicator or notification system. Ask Cline to "build a status page for video renders." It will use `get_render_status` to fetch the data, create a new UI component to display it, and write the necessary polling logic. It handles the whole task, not just one piece of it.

Integrate Your Asset History

The `list_renders` tool returns a paginated list of all videos associated with your Kapwing account. It's a simple way to get a manifest of all your rendered assets. This is perfect for building internal dashboards or asset management tools. Cline can use `list_renders` to fetch the data, then write the code to display it in a table, complete with links to each video. This MCP server makes it a one-prompt job.

Setup guide

Set up Kapwing MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type kapwing-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Kapwing refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "kapwing-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Kapwing. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

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

Connect Kapwing now

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 Cline

You describe the feature, and Cline writes the code. It can create API routes that call `create_render`, build front-end components that poll `get_render_status`, and handle the entire integration.

Yes. After writing the code to call the Kapwing tools, you can ask Cline to write unit or integration tests for it. It understands how to mock the MCP tool calls and verify your code's logic.

Cline is designed to write production-ready code. It will use the `create_render` and `get_render_status` tools within typed functions, handle errors, and follow the patterns of your existing codebase. You always get to review the diff before committing.

No, Vinkius handles authentication. Once you connect the MCP server, your single Vinkius endpoint token authorizes all tool calls. You don't have to manage separate Kapwing keys.

The server transmits your JSON project definitions to the Kapwing API for rendering. It doesn't store this data. The Vinkius platform ensures each transaction is isolated and ephemeral, protecting your project content.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript