How to Use the Cloudinary MCP in CrewAI

Q: How do I assign Cloudinary tools to a specific CrewAI agent?

You pass your Vinkius MCP Server URL in the agent's mcps list. To restrict access, use MCPServerHTTP with a toolfilter so your research agent only gets searchmedialibrary while your moderator agent gets deletemediaresource.

Q: Can CrewAI agents collaborate to optimize Cloudinary storage?

Yes. A monitoring agent can check getcloudinaryusagereport and flag high storage. A second CrewAI agent can then search for bloated files and suggest optimizations based on your active upload presets.

Q: How do CrewAI agents handle large-scale Cloudinary searches?

Agents use searchmedialibrary to run targeted queries. Because CrewAI agents share memory, they can pass search results between themselves to compile lists of assets that need updating.

Deploy autonomous CrewAI agent teams to monitor, tag, and manage your Cloudinary media library.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cloudinary MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous Media Auditing

`get_cloudinary_usage_report` allows your CrewAI auditing agent to monitor your monthly storage and bandwidth metrics. If Cloudinary usage spikes, this agent shares the data with your CrewAI optimization agent to find the root cause. The CrewAI optimization agent then uses `list_media_resources` to identify the largest files in your Cloudinary account. Together, the crew generates a detailed report on which Cloudinary assets are consuming the most bandwidth without any human intervention.

Automated Tagging and Organization

`list_media_tags` and `search_media_library` give your CrewAI categorization team the tools they need to organize assets. A CrewAI researcher agent searches for untagged files, while an editor agent applies the correct taxonomy. By using shared memory, the CrewAI agents remember which tags have been applied across sessions. This prevents duplicate work and ensures your Cloudinary account remains perfectly categorized.

Guardrailed Asset Deletion with MCP Server

`delete_media_resource` is exposed to your CrewAI moderation team with strict execution constraints. A CrewAI monitor agent first checks the asset details using `get_media_resource_details` to verify it is safe to remove. Once verified, the monitor agent escalates the task to the CrewAI moderator agent, who executes the deletion tool. This CrewAI multi-agent hierarchy prevents accidental file loss by requiring verification before any Cloudinary write action is taken.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

You pass your Vinkius MCP Server URL in the agent's `mcps` list. To restrict access, use `MCPServerHTTP` with a `tool_filter` so your research agent only gets `search_media_library` while your moderator agent gets `delete_media_resource`.

Yes. A monitoring agent can check `get_cloudinary_usage_report` and flag high storage. A second CrewAI agent can then search for bloated files and suggest optimizations based on your active upload presets.

Yes. Your CrewAI agents never see your raw Cloudinary API credentials. Vinkius handles the authentication securely on its backend, exposing only the MCP tools via a single, secure endpoint token.

Agents use `search_media_library` to run targeted queries. Because CrewAI agents share memory, they can pass search results between themselves to compile lists of assets that need updating.

The agents only access your Cloudinary usage statistics, asset metadata, and file paths. Vinkius runs this MCP Server in a zero-trust, ephemeral sandbox environment, meaning no media data is cached or stored after the crew finishes its task.

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