---
title: "Cloudinary Asset Management MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/cloudinary/
description: "Search, upload, organize and transform Cloudinary media through its dedicated Asset Management server."
---

# Cloudinary Asset Management MCP: review, setup & limitations · Undominated.ai

> Search, upload, organize and transform Cloudinary media through its dedicated Asset Management server.

[← Explore all mcp servers](/mcp-servers/)

MEDIA MANAGEMENT / Cloudinary

# Cloudinary Asset Management MCP

Search, upload, organize and transform Cloudinary media through its dedicated Asset Management server.

 [See setup guidance ↓](#setup)[Original source ↗](https://cloudinary.com/documentation/cloudinary_llm_mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 1 linked sources
 Publisher Cloudinary
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Upload and manage images, videos, and raw files, with support for advanced search and filtering.”

 [Cloudinary · upstream description ↗](https://cloudinary.com/documentation/cloudinary_llm_mcp) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Provides media-specific search, organization and transformation operations from a single reviewed endpoint.
- OAuth connects the client to a chosen Cloudinary product environment without copying API secrets into the basic setup.
- Cloudinary’s page names a remote Asset Management MCP server and publishes the URL https://asset-management.mcp.cloudinary.com/mcp.
- Remote servers use OAuth by default, with API-key headers as an alternative, except the Analysis server, which the page says does not support API key authentication.

### A good fit for

 - Find and organize a media library.
- Generate transformation URLs or approved derived assets.
- Uploading or searching media in a Cloudinary product environment through a remote MCP client that can complete OAuth
- Not for calling the Analysis MCP server with an API key

### Weigh up before choosing

 - Asset tools can upload, rename or delete media; grant access only to the intended cloud.
- Environment configuration, structured metadata, Analysis and MediaFlows are separate servers with different capabilities or authentication.
- Use the current /mcp endpoint; older /sse configurations are deprecated for Asset Management.
- The Analysis MCP server does not support API key authentication. That exception is stated for Analysis, not copied onto every server in the list.
- The page’s server descriptions sit in a table. Adjacent cells were not joined into a tool list.
- No licence was stated on this page, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- Installing documentation skills does not establish a Cloudinary account connection; operational tools can change or upload media.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Cloudinary’s current server inventory, remote authentication guidance and Asset Management Cursor configuration link.
- https://cloudinary.com/documentation/cloudinary_llm_mcp
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The Asset Management entry includes transformation tools as well as upload/search/delete/rename operations.
- Remote /mcp uses stateless Streamable HTTP and OAuth; implementation language and server licence are not established by the setup page.
- The page documents a Cloudinary Asset Management MCP server and gives the remote URL https://asset-management.mcp.cloudinary.com/mcp.
- Remote MCP servers use OAuth by default. API keys in headers are described for cases where OAuth is not suitable.
- The Analysis MCP server does not support API key authentication and is told to use OAuth. That limit is specific to Analysis.
- The documentation separates Cloudinary skills from operational MCP servers that upload assets, apply transformations and manage metadata.

### Not established by this review

 - Server launch, authenticated tool calls, and release-to-source parity were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://cloudinary.com/documentation/cloudinary_llm_mcp)
 - Use the Asset Management one-click link or the documented remote URL in your client’s MCP settings.
- Finish OAuth and select the intended Cloudinary product environment.
- The JSON uses Cursor’s mcpServers layout; follow the client-specific guide for other hosts.

### Before you start

 - A Cloudinary account and access to the chosen product environment.
- An OAuth-capable remote MCP client.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "cloudinary-asset-mgmt": {
 "url": "https://asset-management.mcp.cloudinary.com/mcp"
 }
 }
} Copy configuration ↗

### Compatibility

Cursor · Claude Code · Claude Desktop · Codex

### Transports

Streamable HTTP

### Remote OAuth

 - Reads media-library data and can upload, rename, delete or derive assets.
- Returns asset information and URLs to the connected client.

### Cost model

Cloudinary storage, delivery and transformation usage follow the account plan; the AI client is separate.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Cloudinary Asset Management MCP setup and scope ↗](https://cloudinary.com/documentation/cloudinary_llm_mcp) Checked 2026-10-14 https://cloudinary.com/documentation/cloudinary_llm_mcp Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Mux MCP Server ↗ Hosted Mux server built on the Code Mode scheme: a documentation search tool plus a code execution tool that runs agent-written TypeScript against the Mux TypeScript SDK (@mux/ts) in an isolated sandbox, covering Video, Data, Robots, System and Webhooks surfaces.](/mcp-servers/mux/)[### Vimeo MCP Server ↗ Vimeo's remote MCP server at mcp.vimeo.com connects an assistant to a Vimeo video library over OAuth: search videos, pull analytics, read transcripts and comments, manage showcases, edit video metadata and privacy, and render videos through Vimeo Create. It is in public beta and requires a Pro plan or above; the publisher excludes destructive actions such as deleting videos, and team access is managed per member.](/mcp-servers/vimeo/)[### Canva MCP ↗ A hosted connection for authorized Canva design discovery, creation, editing and export workflows.](/mcp-servers/canva/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
