How to integrate Cloudinary MCP with Hermes

GET STARTED FOR FREE
Cloudinary logo
Hermes logo
divider

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Cloudinary account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Cloudinary with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Cloudinary with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Cloudinary

Ask your agent to connect to Cloudinary, or simply request any Cloudinary-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Cloudinary connection.

Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Cloudinary or request any Cloudinary-related task. It will prompt you to authenticate and authorize access.

5. Done!

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.

Supported Tools & Triggers

Tools
Create FolderTool to create a new asset folder.
Create Metadata FieldTool to create a new metadata field definition.
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 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 Metadata FieldTool to delete a metadata field by external id.
Delete Resources by Asset IDTool to delete resources by asset ids.
Delete Resources by TagsTool to delete cloudinary assets by tag.
Delete TriggerTool to delete a trigger (webhook notification).
Get Adaptive Streaming ProfilesTool to list adaptive streaming profiles.
Get product environment config detailsTool to get product environment config details.
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 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 by folder.
Get UsageTool to get product environment usage details.
Order Metadata Field DatasourceTool to update ordering of a metadata field datasource.
Ping Cloudinary ServersTool to ping cloudinary servers.
Restore Metadata Field Datasource EntriesTool to restore previously deleted datasource entries for a metadata field.
Search FoldersTool to search asset folders with filtering, sorting, and pagination.
Update FolderTool to rename or move an existing asset folder.
Update Metadata FieldTool to update a metadata field definition by external id.

Way Forward

With Cloudinary connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

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

Codex logo

Codex

Use Cloudinary MCP with Codex

OpenClaw logo

OpenClaw

Use Cloudinary MCP with OpenClaw

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 Hermes?

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

Book a call↗Get started for free