How to connect Cloudinary to Claude Cowork

Trusted by teams atAWSGleanZoomAirtable

30 min · no commitment · see it on your stack

Cloudinary logo
Claude Cowork logo
divider

Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.

This guide walks you through the easiest and most secure way to connect your Cloudinary account to Cowork via Composio Connect, enabling it to create a new folder for event photos, delete derived assets with IDs [123,456], set up upload preset with watermarking, and more such actions on your behalf without compromising your account security.

Also integrate Cloudinary with

Connecting Cloudinary to Claude Cowork

1. Open Customize

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

2. Add the Composio MCP server

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

3. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Cowork

4. Connect your Cloudinary account

Back in Cowork, ask the agent to connect to Cloudinary or give it any Cloudinary-related task.

For example, ask Cowork to:

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

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Cowork, and your Cloudinary account is ready to use.

What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.

With Composio Connect, Cowork can securely access apps like Cloudinary through MCP without you sharing account credentials directly with the agent.

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.

How to build Cloudinary MCP Agent with another framework

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

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