How to integrate Cloudinary MCP with LangChain

This guide walks you through connecting Cloudinary to LangChain using the Composio tool router. By the end, you'll have a working Cloudinary agent that can create a new folder for event photos, delete derived assets with ids [123,456], set up upload preset with watermarking through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Cloudinary account through Composio's Cloudinary MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Cloudinary logoCloudinary
Api Key

Cloudinary is a cloud-based platform for managing, uploading, and transforming images and videos. It streamlines media workflows and delivers optimized assets globally.

108 Tools

Introduction

This guide walks you through connecting Cloudinary to LangChain using the Composio tool router. By the end, you'll have a working Cloudinary agent that can create a new folder for event photos, delete derived assets with ids [123,456], set up upload preset with watermarking through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Cloudinary account through Composio's Cloudinary MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Cloudinary with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Cloudinary project to Composio
  • Create a Tool Router MCP session for Cloudinary
  • Initialize an MCP client and retrieve Cloudinary tools
  • Build a LangChain agent that can interact with Cloudinary
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Cloudinary functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Cloudinary tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['cloudinary']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Cloudinary tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Cloudinary tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "cloudinary-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Cloudinary MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Cloudinary tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Cloudinary related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['cloudinary']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "cloudinary-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Cloudinary related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Cloudinary through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Cloudinary action and event your agent gets out of the box.

Activate Live Stream

Tool to manually activate a Cloudinary live stream.

Create Asset Relations by Asset ID

Tool to add related assets by asset ID.

Create Asset Relations by Public ID

Tool to create relations between assets by public ID.

Create Folder

Tool to create a new asset folder.

Create Image from Text

Tool to create an image from text using Cloudinary's text generation API.

Create Live Stream

Tool to create a new live stream in Cloudinary.

Create Live Stream Output

Tool to create a new live stream output configuration.

Create Metadata Field

Tool to create a new metadata field definition.

Create Metadata Rule

Tool to create a new conditional metadata rule.

Create Multi-Resource Animation

Tool to create an animated image, video, or PDF from a set of images.

Create Slideshow

Tool to create an auto-generated video slideshow from existing Cloudinary assets.

Create Streaming Profile

Tool to create a new adaptive streaming profile in your Cloudinary account.

Create Transformation

Tool to create a new named transformation by assigning a custom name to a set of transformation parameters.

Create Trigger

Tool to create a new webhook trigger for a specified event type.

Create Upload Mapping

Tool to create a new upload mapping folder and URL template.

Create Upload Preset

Tool to create a new upload preset.

Delete Asset Relations by Asset ID

Tool to delete asset relations by asset ID.

Delete Asset Relations by Public ID

Tool to delete asset relations by public ID.

Delete Derived Resources

Tool to delete derived assets.

Delete Metadata Field Datasource Entries

Tool to delete datasource entries for a specified metadata field.

Delete Folder

Tool to delete an empty asset folder.

Delete Live Stream

Tool to delete a live stream from Cloudinary.

Delete Live Stream Output

Tool to delete a live stream output from Cloudinary.

Delete Metadata Field

Tool to delete a metadata field by external ID.

Delete Metadata Rule

Tool to delete a conditional metadata rule by its ID.

Delete Resources by Asset ID

Tool to delete resources by asset IDs.

Delete Resources by Public ID

Tool to delete Cloudinary resources by public ID, prefix, or all resources.

Delete Resources by Tags

Tool to delete Cloudinary assets by tag.

Delete Streaming Profile

Tool 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 Trigger

Tool to delete a trigger (webhook notification).

Delete Upload Mapping

Tool to delete a folder upload mapping.

Delete Upload Preset

Tool to delete an upload preset from the account.

Destroy Asset

Tool to permanently destroy a Cloudinary asset/resource by public ID.

Destroy Asset by ID

Tool to delete an asset by its immutable asset ID.

Explicit Resource Update

Tool to update an existing asset and/or eagerly generate derived transformations using Cloudinary's Explicit API.

Explode Multi-Page Resource

Tool to create derived images from multi-page files (PDF, PSD, TIFF, animated GIF) by exploding them into separate images.

Generate Archive

Tool to create an archive (ZIP or TGZ file) containing a set of assets from your Cloudinary environment.

Get Adaptive Streaming Profiles

Tool to list adaptive streaming profiles.

Get Analysis Task Status

Tool to get the status of an analysis task.

Get product environment config details

Tool to get product environment config details.

Get Live Stream

Tool to get details of a single live stream by ID.

Get Live Stream Output

Tool to get details of a single live stream output.

Get Live Stream Outputs

Tool to get a list of live stream outputs.

Get Live Streams

Tool to get a list of live streams from Cloudinary.

Get Metadata Field By ID

Tool to get a single metadata field definition by external ID.

Get Resource by Asset ID

Get Resource by Asset ID

Get Resource by Public ID

Tool to get details of a single resource by public ID.

Get Resources by Asset Folder

Tool to list assets stored directly in a specified folder.

Get Resources by Context

Tool to retrieve assets with a specified contextual metadata key/value.

Get Resources in Moderation

Tool to retrieve assets in a moderation queue by status.

Get Root Folders

Tool to list all root folders in the product environment.

Get Streaming Profile Details

Tool to get details of a single streaming profile by name.

Get Resource Tags

Tool to list all tags used for a specified resource type.

Get Transformation

Tool to retrieve details of a specific transformation.

Get Transformations

Tool to list all transformations (named and unnamed).

List Webhook Triggers

Tool to list all webhook triggers for event types in your environment.

Get Upload Mapping Details

Tool to retrieve details of a single upload mapping by folder.

Get Upload Mappings

Tool to list all upload mappings.

Get Upload Preset

Tool to retrieve details of a single upload preset by name.

Get Usage

Tool to get product environment usage details.

Get Video Views

Tool to get video analytics views from Cloudinary.

Idle Live Stream

Tool to manually idle a Cloudinary live stream.

List Images

Tool to list image assets from Cloudinary.

List Metadata Fields

Tool to list all structured metadata fields defined in your Cloudinary product environment.

List Metadata Rules

Tool to retrieve all conditional metadata rules defined in your Cloudinary account.

List Raw Files

Tool to list raw assets from Cloudinary.

List Resources by Asset IDs

Tool to retrieve multiple resources by their asset IDs.

List Resources by External IDs

Tool to retrieve resources by their external IDs.

List Resources by Tag

Tool to list resources (assets) with a specified tag.

List Resources by Type

Tool to retrieve resources (assets) by resource type and storage type.

List Resource Types

Tool to list all available resource types in your Cloudinary product environment.

List Upload Presets

Tool to list all upload presets configured in the account.

List Video Assets

Tool to list video assets from Cloudinary.

Manage Context Metadata

Tool to add or remove contextual metadata on Cloudinary assets.

Order Metadata Field Datasource

Tool to update ordering of a metadata field datasource.

Ping Cloudinary Servers

Tool to ping Cloudinary servers.

Publish Resources

Tool to publish Cloudinary assets by public IDs, prefix, or tag.

Rename or Move Resource Public ID

Tool to rename an asset's public ID using Cloudinary's rename endpoint.

Reorder Metadata Field

Tool to change the position of a specific metadata field.

Reorder Metadata Fields

Tool to reorder all metadata fields in the product environment.

Restore Metadata Field Datasource Entries

Tool to restore previously deleted datasource entries for a metadata field.

Restore Deleted Resources

Tool to restore deleted Cloudinary resources by public IDs.

Restore Resources by Asset IDs

Tool to restore backed up assets by asset IDs.

Search Assets

Tool to search and filter assets using powerful query expressions.

Search Datasource in Metadata Field

Tool to search datasource values in a metadata field.

Search Folders

Tool to search asset folders with filtering, sorting, and pagination.

Search All Metadata Field Datasources

Tool to search across all metadata field datasources.

Visual Search Assets

Tool to find images in your asset library based on visual similarity or content.

Show Folder

Tool to list sub-folders within a specified folder.

Update Asset Metadata

Tool to populate or update metadata field values on one or more Cloudinary assets.

Update Folder

Tool to rename or move an existing asset folder.

Update Live Stream

Tool to update a live stream's configuration in Cloudinary.

Update Live Stream Output

Tool to modify an existing live stream output configuration.

Update Metadata Field

Tool to update a metadata field definition by external ID.

Update Metadata Field Datasource

Tool to update the datasource (allowed values) for a metadata field.

Update Metadata Rule

Tool to update an existing conditional metadata rule.

Update Resource by Asset ID

Tool to update asset properties by asset ID in Cloudinary.

Update Resource by Public ID

Tool to update asset properties by public ID in Cloudinary.

Update Resource Tags

Tool to add, remove, replace, or remove all tags for one or more Cloudinary assets.

Update Streaming Profile

Tool to modify an existing adaptive streaming profile's configuration.

Update Transformation (v2)

Tool to update the definition of an existing named transformation.

Update Trigger

Tool to update the callback URL of an existing webhook trigger.

Update Upload Mapping

Tool to update an existing upload mapping by changing its remote URL template.

Update Upload Preset

Tool to update an existing upload preset's configuration settings.

Upload Asset

Tool to upload media assets (images, videos, raw files) to Cloudinary.

Upload File Chunk

Tool to upload a single chunk of a large file to Cloudinary.

Upload File (Auto Detect)

Tool to upload files with automatic resource type detection.

FRAMEWORKS

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 Code logo

Claude Code

Use Cloudinary MCP with Claude Code

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

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

Frequently asked questions

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.

Yes, you can. LangChain 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.

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.

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.

Start with Cloudinary.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Cloudinary tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies