How to integrate Cloudinary MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Cloudinary logo
Claude Code logo
divider

Introduction

Manage your Cloudinary directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Cloudinary with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Cloudinary to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

Supported Tools & Triggers

Tools
Activate Live StreamTool to manually activate a Cloudinary live stream.
Create Asset Relations by Asset IDTool to add related assets by asset ID.
Create Asset Relations by Public IDTool to create relations between assets by public ID.
Create FolderTool to create a new asset folder.
Create Image from TextTool to create an image from text using Cloudinary's text generation API.
Create Live StreamTool to create a new live stream in Cloudinary.
Create Live Stream OutputTool to create a new live stream output configuration.
Create Metadata FieldTool to create a new metadata field definition.
Create Metadata RuleTool to create a new conditional metadata rule.
Create Multi-Resource AnimationTool to create an animated image, video, or PDF from a set of images.
Create SlideshowTool to create an auto-generated video slideshow from existing Cloudinary assets.
Create Streaming ProfileTool to create a new adaptive streaming profile in your Cloudinary account.
Create TransformationTool to create a new named transformation by assigning a custom name to a set of transformation parameters.
Create TriggerTool to create a new webhook trigger for a specified event type.
Create Upload MappingTool to create a new upload mapping folder and URL template.
Create Upload PresetTool to create a new upload preset.
Delete Asset Relations by Asset IDTool to delete asset relations by asset ID.
Delete Asset Relations by Public IDTool to delete asset relations by public ID.
Delete Derived ResourcesTool to delete derived assets.
Delete Metadata Field Datasource EntriesTool to delete datasource entries for a specified metadata field.
Delete FolderTool to delete an empty asset folder.
Delete Live StreamTool to delete a live stream from Cloudinary.
Delete Live Stream OutputTool to delete a live stream output from Cloudinary.
Delete Metadata FieldTool to delete a metadata field by external ID.
Delete Metadata RuleTool to delete a conditional metadata rule by its ID.
Delete Resources by Asset IDTool to delete resources by asset IDs.
Delete Resources by Public IDTool to delete Cloudinary resources by public ID, prefix, or all resources.
Delete Resources by TagsTool to delete Cloudinary assets by tag.
Delete Streaming ProfileTool to delete a custom streaming profile or revert a built-in profile to original settings.
Delete Transformation (v2)Tool to delete a named transformation from your Cloudinary account.
Delete TriggerTool to delete a trigger (webhook notification).
Delete Upload MappingTool to delete a folder upload mapping.
Delete Upload PresetTool to delete an upload preset from the account.
Destroy AssetTool to permanently destroy a Cloudinary asset/resource by public ID.
Destroy Asset by IDTool to delete an asset by its immutable asset ID.
Explicit Resource UpdateTool to update an existing asset and/or eagerly generate derived transformations using Cloudinary's Explicit API.
Explode Multi-Page ResourceTool to create derived images from multi-page files (PDF, PSD, TIFF, animated GIF) by exploding them into separate images.
Generate ArchiveTool to create an archive (ZIP or TGZ file) containing a set of assets from your Cloudinary environment.
Get Adaptive Streaming ProfilesTool to list adaptive streaming profiles.
Get Analysis Task StatusTool to get the status of an analysis task.
Get product environment config detailsTool to get product environment config details.
Get Live StreamTool to get details of a single live stream by ID.
Get Live Stream OutputTool to get details of a single live stream output.
Get Live Stream OutputsTool to get a list of live stream outputs.
Get Live StreamsTool to get a list of live streams from Cloudinary.
Get Metadata Field By IDTool to get a single metadata field definition by external ID.
Get Resource by Asset IDGet Resource by Asset ID
Get Resource by Public IDTool to get details of a single resource by public ID.
Get Resources by Asset FolderTool to list assets stored directly in a specified folder.
Get Resources by ContextTool to retrieve assets with a specified contextual metadata key/value.
Get Resources in ModerationTool to retrieve assets in a moderation queue by status.
Get Root FoldersTool to list all root folders in the product environment.
Get Streaming Profile DetailsTool to get details of a single streaming profile by name.
Get Resource TagsTool to list all tags used for a specified resource type.
Get TransformationTool to retrieve details of a specific transformation.
Get TransformationsTool to list all transformations (named and unnamed).
List Webhook TriggersTool to list all webhook triggers for event types in your environment.
Get Upload Mapping DetailsTool to retrieve details of a single upload mapping by folder.
Get Upload MappingsTool to list all upload mappings.
Get Upload PresetTool to retrieve details of a single upload preset by name.
Get UsageTool to get product environment usage details.
Get Video ViewsTool to get video analytics views from Cloudinary.
Idle Live StreamTool to manually idle a Cloudinary live stream.
List ImagesTool to list image assets from Cloudinary.
List Metadata FieldsTool to list all structured metadata fields defined in your Cloudinary product environment.
List Metadata RulesTool to retrieve all conditional metadata rules defined in your Cloudinary account.
List Raw FilesTool to list raw assets from Cloudinary.
List Resources by Asset IDsTool to retrieve multiple resources by their asset IDs.
List Resources by External IDsTool to retrieve resources by their external IDs.
List Resources by TagTool to list resources (assets) with a specified tag.
List Resources by TypeTool to retrieve resources (assets) by resource type and storage type.
List Resource TypesTool to list all available resource types in your Cloudinary product environment.
List Upload PresetsTool to list all upload presets configured in the account.
List Video AssetsTool to list video assets from Cloudinary.
Manage Context MetadataTool to add or remove contextual metadata on Cloudinary assets.
Order Metadata Field DatasourceTool to update ordering of a metadata field datasource.
Ping Cloudinary ServersTool to ping Cloudinary servers.
Publish ResourcesTool to publish Cloudinary assets by public IDs, prefix, or tag.
Rename or Move Resource Public IDTool to rename an asset's public ID using Cloudinary's rename endpoint.
Reorder Metadata FieldTool to change the position of a specific metadata field.
Reorder Metadata FieldsTool to reorder all metadata fields in the product environment.
Restore Metadata Field Datasource EntriesTool to restore previously deleted datasource entries for a metadata field.
Restore Deleted ResourcesTool to restore deleted Cloudinary resources by public IDs.
Restore Resources by Asset IDsTool to restore backed up assets by asset IDs.
Search AssetsTool to search and filter assets using powerful query expressions.
Search Datasource in Metadata FieldTool to search datasource values in a metadata field.
Search FoldersTool to search asset folders with filtering, sorting, and pagination.
Search All Metadata Field DatasourcesTool to search across all metadata field datasources.
Visual Search AssetsTool to find images in your asset library based on visual similarity or content.
Show FolderTool to list sub-folders within a specified folder.
Update Asset MetadataTool to populate or update metadata field values on one or more Cloudinary assets.
Update FolderTool to rename or move an existing asset folder.
Update Live StreamTool to update a live stream's configuration in Cloudinary.
Update Live Stream OutputTool to modify an existing live stream output configuration.
Update Metadata FieldTool to update a metadata field definition by external ID.
Update Metadata Field DatasourceTool to update the datasource (allowed values) for a metadata field.
Update Metadata RuleTool to update an existing conditional metadata rule.
Update Resource by Asset IDTool to update asset properties by asset ID in Cloudinary.
Update Resource by Public IDTool to update asset properties by public ID in Cloudinary.
Update Resource TagsTool to add, remove, replace, or remove all tags for one or more Cloudinary assets.
Update Streaming ProfileTool to modify an existing adaptive streaming profile's configuration.
Update Transformation (v2)Tool to update the definition of an existing named transformation.
Update TriggerTool to update the callback URL of an existing webhook trigger.
Update Upload MappingTool to update an existing upload mapping by changing its remote URL template.
Update Upload PresetTool to update an existing upload preset's configuration settings.
Upload AssetTool to upload media assets (images, videos, raw files) to Cloudinary.
Upload File ChunkTool to upload a single chunk of a large file to Cloudinary.
Upload File (Auto Detect)Tool to upload files with automatic resource type detection.

What is the Cloudinary MCP server, and what's possible with it?

The Cloudinary MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Cloudinary account. It provides structured and secure access to your digital asset management system, so your agent can perform actions like organizing folders, creating metadata fields, managing upload presets, and handling asset deletion on your behalf.

  • Automated folder and asset organization: Easily instruct your agent to create new asset folders or remove empty ones, keeping your Cloudinary library tidy and structured.
  • Metadata management: Let your agent create custom metadata fields or delete obsolete ones, extending and refining your asset tagging and search capabilities.
  • Preset and upload mapping creation: Have your agent set up upload presets with specific options or define dynamic folder mappings, automating consistent upload processes across your assets.
  • Resource and derived asset cleanup: Direct your agent to permanently delete assets by ID or remove unnecessary derived resources, ensuring your storage stays efficient and clutter-free.
  • Datasource entry management: Ask your agent to inactivate or delete specific datasource entries from metadata fields, keeping your metadata schema accurate and up to date.

Connecting Cloudinary via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Cloudinary) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Cloudinary account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["cloudinary"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http cloudinary-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Cloudinary. This URL will be used to connect Claude Code to Cloudinary.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Cloudinary
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Cloudinary MCP to Claude Code

bash
claude mcp add --transport http cloudinary-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (cloudinary-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Cloudinary MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your cloudinary-composio entry in the list
  • This confirms that Claude Code can now access Cloudinary tools

If everything is wired up, you should see your cloudinary-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Cloudinary

The first time you try to use Cloudinary tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Cloudinary
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Cloudinary authorization flow
  • Return to the terminal and start using Cloudinary through Claude Code

Once authenticated, you can ask Claude Code to perform Cloudinary operations in natural language. For example:

  • "Create a new folder for event photos"
  • "Delete derived assets with IDs [123,456]"
  • "Set up upload preset with watermarking"

Complete Code

Here's the complete code to get you started with Cloudinary and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["cloudinary"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http cloudinary-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Cloudinary with Claude Code using Composio's MCP server. Now you can interact with Cloudinary directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Cloudinary operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Cloudinary operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Cloudinary MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Cloudinary MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Cloudinary MCP with Claude Agent SDK

Claude Cowork logo

Claude Cowork

Use Cloudinary MCP with Claude Cowork

Codex logo

Codex

Use Cloudinary MCP with Codex

OpenClaw logo

OpenClaw

Use Cloudinary MCP with OpenClaw

Hermes logo

Hermes

Use Cloudinary MCP with Hermes

CLI logo

CLI

Use Cloudinary MCP with CLI

Google ADK logo

Google ADK

Use Cloudinary MCP with Google ADK

LangChain logo

LangChain

Use Cloudinary MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Cloudinary MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Cloudinary MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Cloudinary MCP with LlamaIndex

CrewAI logo

CrewAI

Use Cloudinary MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Cloudinary MCP?

With a standalone Cloudinary MCP server, the agents and LLMs can only access a fixed set of Cloudinary tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Cloudinary and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Cloudinary tools.

Can I manage the permissions and scopes for Cloudinary while using Tool Router?

Yes, absolutely. You can configure which Cloudinary scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Cloudinary data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗