Claude Cloudinary Asset Management connectorWhat Claude can do in your Cloudinary Asset Management account.
The Claude Cloudinary Asset Management connector exposes 23 tools: 11 for reading, 12 for writing. It is a desktop extension for Claude Desktop, keyed to your API credentials. Below: what Claude reads, what it can alter or delete, and how it differs from the remote Cloudinary connector.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for whoever runs the media library
Cleaning up a media library usually means a long stint in the console: filtering by tag, renaming, moving folders one by one. With this extension installed in Claude Desktop, you describe the result you want and Claude calls the matching Cloudinary tools itself, from search to transformation, against your own product environment.
Find anything, even without a tag. search-assets filters by attributes with a query language, and visual-search-assets looks for look-alike images from a URL, an existing asset or a plain description.
Reorganise in bulk. A rebrand means a new folder tree: create-folder prepares it, move-folder carries whole folders and their assets across, and asset-update retags what moved.
Produce the right variant. Before touching an image, get-tx-reference loads Cloudinary's transformation reference, then transform-asset builds the derived version on Cloudinary.
How it differs from the other Cloudinary entry in the directory: that one is a remote connector, while this one is a desktop extension that runs on Claude Desktop and authenticates with your API key and secret. It also adds the transformation reference and transformation tools. What it does not do: it never acts on a schedule, so nothing happens when a file lands. Event-driven pipelines are a job for the automation tools on the Integrations hub.
Five words before you plug it in
The vocabulary you will meet in Claude Desktop.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named action the connector hands to Claude. Claude picks the ones it needs by itself; the directory sheet lists all of them by name.
- Authorization
- The access you hand over so Claude can act on the account. Here it takes the form of your Cloudinary API key and secret.
- Approval
- The confirmation Claude waits for in the chat before it goes ahead with anything that changes an account on your behalf.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service at all.
Plug Cloudinary Asset Management into Claude in three steps
- 01
Open the connector list in Claude Desktop
This one runs as a desktop extension, so start in Claude Desktop: open Customize, then Connectors, and find Cloudinary Asset Management. On a Team or Enterprise workspace, an Owner or Primary Owner enables it first.
- 02
Install and connect
Click Connect on its row. Cloudinary documents the extension as a bundle you can also drag onto Claude Desktop. If the link ever breaks, Disconnect it and connect again.
- 03
Hand over the right credentials
Cloudinary lists three required values: your cloud name, API key and API secret. They decide what the extension can reach. All three are marked as required, and there is no browser sign-in to fall back on.
The 23 tools, sorted by what they do
Cloudinary Asset Management gives Claude 23 tools: 11 that read your account, 12 that change something in it.
Two groups: what Claude reads and what it can alter. Names stay in English, exactly as Claude shows them.
- 11 read
- 12 write
What Claude reads (11)
11 toolsEleven tools that list, search, inspect or pull a copy without touching the library.
download-asset-backup
Retrieves a stored backup of a given asset, which is useful when the current version is not the one you need.
list-images
Returns the image assets of your account, which Claude can narrow down by tag, by prefix or by a list of specific public IDs.
list-videos
Brings back your video assets, again with tag, prefix or public ID filters, so Claude can tell you what footage already exists.
list-files
Shows the raw assets, meaning files that are neither images nor videos, such as documents, with the same filtering options as the other lists.
get-asset-details
Pulls every detail of a single asset from its asset ID, so Claude can answer precise questions about it without guessing.
list-tags
Gathers all the tags currently in use in your Cloudinary account, a quick map of how the library is labelled, without changing a single asset.
get-usage-details
Reports where your product environment stands on storage, credits, bandwidth, requests, resource count and add-on usage. It is a status report you can ask for at any point.
search-folders
Finds folders whose attributes match an expression. Results stop at 2000, and with no parameters it returns the 50 most recently created folders.
search-assets
Queries the library through a query interface to filter assets: one request narrows the selection and brings back the details of every match.
visual-search-assets
Returns images that look like a reference you supply in one of three ways: an image URL, the asset ID of an existing image, or a text description.
get-tx-reference
Brings Cloudinary's full transformation documentation into the conversation.
What Claude changes (12)
12 toolsTwelve tools that add, alter, move or delete things in your product environment. No source details their confirmation; the general rule below applies.
upload-asset
Approval: see the rulePuts an image, a video or a raw file into your Cloudinary product environment.
asset-rename
Approval: see the ruleGives an existing asset a new public ID and can adjust other metadata at the same time.
generate-archive
Approval: see the rulePacks a set of assets from your product environment into a ZIP or TGZ archive that can then be downloaded in one go.
delete-asset
Approval: see the ruleRemoves an asset for good, addressed by its immutable asset ID rather than by its name or folder.
asset-update
Approval: see the ruleAlters the metadata, tags and other attributes of an asset identified by its asset ID, whatever its current public ID, display name or folder.
delete-derived-assets
Approval: see the ruleErases derived resources, the transformed versions Cloudinary generated from an original, using their derived resource IDs.
create-asset-relations
Approval: see the ruleRelates one asset to others by their asset IDs. The link runs both ways, so each of the other assets also lists the first as related.
delete-asset-relations
Approval: see the ruleRemoves the relation between an asset and others, given by asset ID, and the removal applies on both sides of each link.
move-folder
Approval: see the ruleRelocates or renames an entire folder, along with every asset it holds, to a new place in the media library.
create-folder
Approval: see the ruleAdds a new, empty folder, ready to receive uploads or moved assets.
delete-folder
Approval: see the ruleRemoves a folder from the media library together with all the assets inside it, not just the empty shell.
transform-asset
Approval: see the ruleGenerates derived versions of an existing asset on Cloudinary, using the explicit API.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account in your place. That matters here: twelve tools can alter or delete media, and none has a documented confirmation of its own.
On a Team or Enterprise workspace, owners decide whether members may let some actions run without being asked each time, and they can cap what a connector may do for the whole organisation, keeping reading and closing writing for instance. That setting binds everyone. Claude works with the reach of the credentials you supplied, nothing beyond. The official read-only or write-delete label per tool appears only in a signed-in account's settings.
Which plans can use it
None of the 819 sheets in the official directory shows availability by plan. That answer, connector by connector, is published nowhere: a real gap in the catalogue.
The general rule is public. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organisation before members can connect. For the live status, open the Cloudinary Asset Management sheet in the official directory from your own account.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, and nothing starts by itself when a file is uploaded or a folder fills up.
Only Cloudinary documents this extension, through its repository and its published package; neither Claude's help centre nor Anthropic's developer docs cover it. The tool list is an observed floor, and the directory's verification badge is not a security audit: Anthropic says on every sheet that it does not control the tools a publisher exposes. It runs on Claude Desktop only, as an extension on your machine. For another sheet read the same way, see the Claude agility-cms connector.
Need help connecting Cloudinary Asset Management to Claude?
A person reads every message.