How to Use the CloudConvert MCP in CrewAI

Q: How do I add CloudConvert to my CrewAI agents?

You pass the MCP Server URL directly into the mcps parameter of your agent definition. CrewAI handles the connection and tool registration for you.

Q: Does CloudConvert allow filtered tool access in CrewAI?

It does. You can use the toolfilter in your CrewAI setup to restrict which tools specific agents can access, keeping your conversion setup secure.

Deploy autonomous file conversion crews with CrewAI. Let specialized agents handle your document processing from start to finish.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CloudConvert MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run conversion crews with CrewAI

Assign `create_simple_job` to a specialized worker agent. This agent focuses only on formatting, while other agents handle the file gathering and delivery. It delegates the work based on your crew configuration. You get a clean separation of duties where one agent manages the conversion lifecycle independently.

Cancel jobs through CrewAI agents

If your monitor agent detects a change in plans, it triggers `cancel_job` immediately. This prevents wasted credits and stops unnecessary processing on the server. Your agents act as a feedback loop. They monitor the conversion status and intervene whenever the situation changes in your environment.

Audit conversion history in CrewAI

Use `list_jobs` to let your analyst agent review previous activity. It keeps a record of all processed files and identifies trends in your conversion volume. This provides your agents with a memory of past operations. They learn from the history to better manage your future document processing needs.

Setup guide

Set up CloudConvert 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 CloudConvert tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent CloudConvert 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="CloudConvert Analyst",
        goal="Access and analyze CloudConvert data via MCP.",
        backstory="Expert analyst with direct CloudConvert access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent CloudConvert 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 CloudConvert. 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 CloudConvert 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 CloudConvert MCP in CrewAI

You pass the MCP Server URL directly into the `mcps` parameter of your agent definition. CrewAI handles the connection and tool registration for you.

Yes, CrewAI uses shared memory between agents. Once one agent finishes a job, the output data is available to the rest of the crew for subsequent steps.

It does. You can use the `tool_filter` in your CrewAI setup to restrict which tools specific agents can access, keeping your conversion setup secure.

The system automatically purges your source and output files shortly after the task finishes. The server does not maintain long-term storage of your processed documents.

We use a hardened, sandboxed execution environment for all conversion tasks. Your document data is processed in a memory-only space that is destroyed immediately upon task completion, ensuring zero persistence.

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