How to Use the Kapwing MCP in CrewAI

Q: How do I give my CrewAI agents access to Kapwing?

Pass the endpoint URL directly into the mcps array when defining your Agent. The framework automatically discovers the available rendering tools and assigns them to the agent's capabilities.

Q: Can I restrict Kapwing access to a specific CrewAI agent?

Yes, you can use MCPServerHTTP from crewai.mcp and apply a toolfilter. This lets you give the creation tool to an editor agent while restricting the list tool to an auditor agent.

Deploy autonomous CrewAI agents to manage your Kapwing video campaigns via this MCP Server.

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 CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assign Video Creation to CrewAI Agents

Passing the `create_render` tool to a specialized agent allows it to generate videos from structured JSON. The agent defines the project width, height, and individual layers based on its assigned research. It acts as an autonomous video editor. A separate copywriter agent can draft the text overlays, while the editor agent compiles the final JSON configuration. They collaborate to produce marketing assets without you touching a timeline.

Delegate Status Monitoring

The `get_render_status` tool checks the progress of an active job and retrieves the final MP4 link. It requires the specific ID generated during the initial creation phase. You can assign a dedicated monitor agent to handle this task. It periodically checks the endpoint, waits for the completion signal, and then hands the finished URL over to a distribution agent for publishing.

Index Past Campaigns via MCP Server

You trigger the `list_renders` tool to pull a complete history of account media. It returns the metadata for every video produced under your API limits. An analytics agent can parse this historical data to audit past outputs. It reviews the dimensions and configurations of previous renders to maintain brand consistency across your entire channel.

Setup guide

Set up Kapwing MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Kapwing tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Kapwing Analyst",
    goal="Access and analyze Kapwing data via MCP.",
    backstory="Expert analyst with direct Kapwing access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Kapwing transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Kapwing Analyst",
        goal="Access and analyze Kapwing data via MCP.",
        backstory="Expert analyst with direct Kapwing access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Kapwing transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

Pass the endpoint URL directly into the `mcps` array when defining your Agent. The framework automatically discovers the available rendering tools and assigns them to the agent's capabilities.

Yes, you can use `MCPServerHTTP` from `crewai.mcp` and apply a `tool_filter`. This lets you give the creation tool to an editor agent while restricting the list tool to an auditor agent.

They use shared memory. The first agent creates the job and logs the render ID. The second agent reads that ID from memory and uses it to poll the status endpoint.

No, the MCP standardizes the interface. You just provide the connection details, and the framework translates the tool schemas into native Python functions.

Nobody but you and the destination API. Vinkius processes your text overlays, video links, and project configurations through stateless V8 isolates. The memory clears the moment the connection drops, ensuring your proprietary marketing assets never sit on our disks.

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