Claude Cloudinary connectorWhat Claude can do in your Cloudinary account.
The Claude Cloudinary connector exposes 22 tools. 4 are documented as reading your media library, 5 as changing it, and 13 are described by no source at all. Below: what Claude can safely do with your images and videos, and the large part nobody documents.
Verified Trustpilot reviews · AI, automation & growth agency
What Claude does with your Cloudinary library
Media libraries grow faster than anyone tags them. With the connector, you ask Claude in plain words for the product shots uploaded last week, the videos in a campaign folder or the details of one asset, and it looks them up in your Cloudinary account. It can also upload a file, add tags, rename or remove an asset.
Find the right file fast. search-assets answers requests like "images tagged product from the last 7 days", and get-asset-details tells you everything about the one you pick.
Tidy as you go. Claude can add tags with asset-update, give an asset a clearer public ID, or open a new folder for a campaign with create-folder.
Keep an eye on usage. get-usage-details returns your account's usage statistics, useful before a big upload.
What to know first: Cloudinary does not describe its tools one by one, so 13 of the 22 names on the directory sheet have no documented behaviour, and this page does not guess it from the names. This connector is Cloudinary's asset management server only; its configuration, metadata, analysis and automation servers are separate. Nothing runs on its own either: Claude acts only while you talk to it. For uploads that fire on every new form entry, see our Cloudinary n8n integration page.
Five words before you connect
The vocabulary around this connector, explained once.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector gives Claude. Claude picks which ones to call by itself, and the directory lists them by name.
- Authorization
- Cloudinary's sign-in screen, where you grant Claude access and pick the product environment it will use. Once per person, revocable.
- Approval
- The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it matters.
- MCP
- The open standard connectors run on: it is what lets an assistant like Claude talk to an outside service such as Cloudinary.
Connect Cloudinary to Claude in three steps
- 01
Find Cloudinary in Claude
In Claude's settings, go to Customize then Connectors and look up Cloudinary. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can sign in.
- 02
Sign in to Cloudinary
Click Connect on its row and log in within the window Cloudinary opens. If the connection breaks later, Disconnect and connect again from the same row in Claude's settings.
- 03
Pick the right environment
Cloudinary asks which product environment, or cloud, you want to use. Choose carefully: the screen belongs to Cloudinary, not to Claude, and it decides which library Claude works in and what the access covers.
The 22 tools, split by what is documented
Cloudinary gives Claude 22 tools: 4 that read your account, 5 that change something in it, and 13 no official source describes.
Three groups: what Claude reads, what it changes, and the 13 names no source explains. Names stay exactly as Claude shows them.
- 4 read
- 5 write
- 13 not documented
What Claude reads (4)
4 toolsFour lookups Cloudinary illustrates with examples: search, one asset, videos in a folder, account usage.
list-videos
Lists the video assets in your library, for example all videos stored in a marketing folder, which is the example Cloudinary uses.
get-asset-details
Returns the details of one asset from its ID, so Claude can tell you what the file is, how it is named and how it is organised.
get-usage-details
Returns the usage statistics of your Cloudinary account, the figures to watch as your library and traffic grow.
search-assets
Searches your assets by criteria such as tags and upload date, as in Cloudinary's example of images tagged product from the last 7 days.
What Claude changes (5)
5 toolsUpload, rename, delete, update and create a folder. No source spells out their confirmation, so the general rule below applies.
upload-asset
Approval: see the ruleSends an image, a video or a raw file into your Cloudinary library, one of the three kinds of file Cloudinary names for this server.
asset-public_id-rename
Approval: see the ruleRenames an asset, meaning its public ID. Cloudinary lists renaming among the everyday tasks of this server.
delete-asset
Approval: see the ruleRemoves an asset from your library. Cloudinary names deletion alongside renaming as something the server makes easy.
asset-update
Approval: see the ruleChanges an asset's properties, for example adding tags such as featured or homepage, which Cloudinary gives as its example.
create-folder
Approval: see the ruleCreates a new folder in your media library, to keep a campaign or a product range together.
Undocumented (13)
13 toolsNames on the directory sheet with no official description. We do not infer what they do from how they are spelled.
download-asset
This name appears on the directory sheet, and Cloudinary publishes no description of it. Its usage examples and its server overview never mention it, so this page says nothing about what it returns or where.
generate-archive
Cloudinary gives one example prompt about producing a ZIP archive of tagged images, but no source says whether this tool stores anything in your account or only hands back a file. So its effect stays undocumented here.
download-asset-backup
Only the name is public. No sentence from Cloudinary or from Anthropic describes this tool, so we would rather flag the gap than fill it with an assumption drawn from the wording.
list-images
The directory shows this name next to a documented tool for videos, yet no source describes this one. Cloudinary's example covers video listing only, and we do not extend it to a neighbouring name.
list-files
Here again, nothing beyond the name: no source describes it, whether from Cloudinary or from Claude. The server overview talks about raw files in general terms, without linking that statement to any tool.
list-tags
Cloudinary mentions tags for organising a library, but no source describes what this particular name does or returns. This page leaves it undocumented rather than guessing.
delete-derived-assets
No official source describes this name. Cloudinary's overview and examples never mention it, so the page makes no claim about what it acts on.
create-asset-relations
The directory lists the name and nothing more. Neither Cloudinary's documentation nor its repository explains what an asset relation is in this server, so the page stays silent on its effect.
delete-asset-relations
No source documents this name either. Its counterpart above is just as undocumented, so there is nothing reliable to say about either one, and this page does not try.
move-folder
Listed on the sheet, this name has no description anywhere. Cloudinary talks about folders for organising assets, but never ties that sentence to this tool, so its behaviour is not documented.
delete-folder
No official text describes what this tool does, and Cloudinary's examples do not cover it. Whether it touches the assets inside a folder is not said anywhere we could read.
search-folders
Cloudinary says the server supports advanced search and filtering, without naming which tools do what. No source covers this one specifically, so the page makes no claim about it.
visual-search-assets
Neither the server overview nor the usage examples mention this name, and no source describes it. What it searches and how stays undocumented, and we will not read a feature into the label.
What Claude checks with you first
By default, Claude pauses and asks before each action it takes on an account for someone, right in the conversation.
On Team and Enterprise workspaces, owners decide whether members may let some actions run without a prompt each time. They can also narrow a connector for the whole organization, for example searching allowed and uploading or deleting blocked, and nobody lifts that from a personal account. Claude works with the rights of the person who connected, nothing more. The official per-tool label, read only versus write and delete, exists only in a signed-in account's settings, which matters here since so many tools are undocumented.
Which Claude plans include it
None of the 819 sheets in the official directory states plan availability. That answer is published nowhere, connector by connector.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before members connect. Cloudinary's own subscription is a separate matter that no source ties to Claude. To check the live state for your account, open the connector's sheet in the directory.
Where the Claude Cloudinary connector stops
A connector is not an automation. Claude calls these tools while replying, so nothing happens when someone uploads a file on their own.
Cloudinary describes its asset management server as a whole and gives example prompts, but never explains its tools one by one. A tool list is also an observed floor, not a promise, and the partner badge is not a security audit; Anthropic says on every sheet that it does not control a publisher's tools. No Claude help article covers this connector. For a case where official sources contradict each other openly, see our Claude gmail connector page.
Need help connecting Cloudinary to Claude?
A person reads every message.
