Cloudinary Asset Management

Name: Cloudinary Asset Management
Author: cloudinary

by cloudinaryversion 0.11.6i★ –iComputer or cloud

Registry nameio.github.cloudinary/asset-management-mcp

Install

Overview

Description from the maker (original English)

Upload, generate, organize, search, and transform images, videos, and files with AI-powered tools.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Search & AI memory
You need to fill in: CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET, cloudinary-cloud-name, cloudinary-api-key, cloudinary-api-secret

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET, cloudinary-cloud-name, cloudinary-api-key, cloudinary-api-secret

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "asset-management": {
      "command": "npx",
      "args": [
        "-y",
        "@cloudinary/asset-management-mcp"
      ],
      "env": {
        "CLOUDINARY_CLOUD_NAME": "your-value",
        "CLOUDINARY_API_KEY": "your-value",
        "CLOUDINARY_API_SECRET": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http asset-management https://asset-management.mcp.cloudinary.com/mcp --header 'cloudinary-cloud-name: your-value' --header 'cloudinary-api-key: your-value' --header 'cloudinary-api-secret: your-value'

Or run it on your computer

claude mcp add asset-management --env CLOUDINARY_CLOUD_NAME=your-value --env CLOUDINARY_API_KEY=your-value --env CLOUDINARY_API_SECRET=your-value -- npx -y @cloudinary/asset-management-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "asset-management": {
      "url": "https://asset-management.mcp.cloudinary.com/mcp",
      "headers": {
        "cloudinary-cloud-name": "your-value",
        "cloudinary-api-key": "your-value",
        "cloudinary-api-secret": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "asset-management": {
      "command": "npx",
      "args": [
        "-y",
        "@cloudinary/asset-management-mcp"
      ],
      "env": {
        "CLOUDINARY_CLOUD_NAME": "your-value",
        "CLOUDINARY_API_KEY": "your-value",
        "CLOUDINARY_API_SECRET": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "asset-management": {
      "type": "http",
      "url": "https://asset-management.mcp.cloudinary.com/mcp",
      "headers": {
        "cloudinary-cloud-name": "your-value",
        "cloudinary-api-key": "your-value",
        "cloudinary-api-secret": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "asset-management": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cloudinary/asset-management-mcp"
      ],
      "env": {
        "CLOUDINARY_CLOUD_NAME": "your-value",
        "CLOUDINARY_API_KEY": "your-value",
        "CLOUDINARY_API_SECRET": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CLOUDINARY_CLOUD_NAME required env
Your Cloudinary cloud name. Find it in your Cloudinary Dashboard.
CLOUDINARY_API_KEY secret required env
Your Cloudinary API key. Found in Dashboard > Settings > Access Keys.
CLOUDINARY_API_SECRET secret required env
Your Cloudinary API secret. Found in Dashboard > Settings > Access Keys.
cloudinary-cloud-name required HTTP header
Your Cloudinary cloud name. Find it in your Cloudinary Dashboard.
cloudinary-api-key secret required HTTP header
Your Cloudinary API key. Found in Dashboard > Settings > Access Keys.
cloudinary-api-secret secret required HTTP header
Your Cloudinary API secret. Found in Dashboard > Settings > Access Keys.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account cloudinary, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 269 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7258 servers in this category
Published to the registry more recently than 95% of the other 7258 servers in this category
Basic checks equal to or better than 100% of the other 7258 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Cloudinary Asset Management safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET, cloudinary-cloud-name, cloudinary-api-key, cloudinary-api-secret

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.11.6) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Cloudinary Asset Management MCP Server

Summary

Cloudinary Asset Management MCP Server
Installation
Configuration
Authentication
Available Tools
Custom Tools
Progressive Discovery
Development
Building from Source
Contributions

Installation

The MCP server requires Node.js 20.19.0 or later.

Claude Desktop

Install the MCP server as a Desktop Extension using the pre-built mcp-server.mcpb file:

Simply drag and drop the mcp-server.mcpb file onto Claude Desktop to install the extension.

The MCP bundle package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.

[!NOTE]

MCP bundles provide a streamlined way to package and distribute MCP servers. Learn more about Desktop Extensions.

Cursor

Or manually:

Open Cursor Settings
Select Tools and Integrations
Select New MCP Server
If the configuration file is empty paste the following JSON into the MCP Server Configuration:

"command": "npx", "args": [ "@cloudinary/asset-management-mcp", "start", "--api-key", "", "--api-secret", "", "--cloud-name", "" ] }

Claude Code CLI

claude mcp add CloudinaryAssetMgmt -- npx -y @cloudinary/asset-management-mcp start --api-key  --api-secret  --cloud-name

Gemini

gemini mcp add CloudinaryAssetMgmt -- npx -y @cloudinary/asset-management-mcp start --api-key  --api-secret  --cloud-name

Windsurf

Refer to Official Windsurf documentation for latest information

Open Windsurf Settings
Select Cascade on left side menu
Click on Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)
Click on View raw config to open up the mcp configuration file.
If the configuration file is empty paste the full json

"command": "npx", "args": [ "@cloudinary/asset-management-mcp", "start", "--api-key", "", "--api-secret", "", "--cloud-name", "" ] }

</details>

VS Code

Or manually:

Refer to Official VS Code documentation for latest information

Open Command Palette
Search and open MCP: Open User Configuration. This should open mcp.json file
If the configuration file is empty paste the full json

"command": "npx", "args": [ "@cloudinary/asset-management-mcp", "start", "--api-key", "", "--api-secret", "", "--cloud-name", "" ] }

Stdio installation via npm To start the MCP server, run:

npx @cloudinary/asset-management-mcp start --api-key  --api-secret  --cloud-name

For a full list of server arguments, run:

npx @cloudinary/asset-management-mcp --help

Configuration

Environment Variables

The MCP server supports the following environment variables:

Variable	Description	Required
`CLOUDINARY_CLOUD_NAME`	Your Cloudinary cloud name	Yes
`CLOUDINARY_API_KEY`	Your Cloudinary API key	Yes
`CLOUDINARY_API_SECRET`	Your Cloudinary API secret	Yes
`CLOUDINARY_URL`	Complete Cloudinary URL (alternative to individual vars)	No
`CLOUDINARY_COLLECT_HEADERS`	Collect API response headers (see below)	No
`CLOUDINARY_MCP_APPS`	Override MCP Apps default (see MCP Apps)	No

CLOUDINARY_URL Format

You can use a single CLOUDINARY_URL instead of individual variables:

CLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME

Response Header Collection

You can configure the server to include Cloudinary API response headers (such as x-request-id and rate limit info) in tool output. This is useful for debugging and monitoring.

Set CLOUDINARY_COLLECT_HEADERS to control which headers are collected:

# Collect all response headers

CLOUDINARY_COLLECT_HEADERS=true

Collect specific headers by exact name (comma-separated)

CLOUDINARY_COLLECT_HEADERS=x-request-id,x-featureratelimit-limit,x-featureratelimit-remaining

Mix exact names, prefix matching, and regex matching

CLOUDINARY_COLLECT_HEADERS=x-request-id,prefix:x-featureratelimit-

Header matching specs

Each entry in the comma-separated list is matched against response header names:

Format	Example	Behaviour
exact name	`x-request-id`	matches only `x-request-id`
`prefix:`	`prefix:x-featureratelimit-`	matches any header starting with `x-featureratelimit-`
`regex:`	`regex:ratelimit`	matches any header whose name contains `ratelimit`

You can also set this via the CLOUDINARY_URL query parameter:

CLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME?collect_headers=true

When enabled, collected headers appear in an _headers field in the tool response. When not set, no headers are collected and responses are unchanged.

MCP Apps

The server can expose interactive MCP UI Apps (spec-aligned with io.modelcontextprotocol/ui) that hosts can render alongside tool results — for example, an asset gallery for list results, a single-asset detail view, and an upload UI.

Apps are enabled by default. Use the --mcp-apps flag (available on both start and serve) or the CLOUDINARY_MCP_APPS environment variable to override this behaviour:

Value	Effect
unset	Default — all apps enabled
bare `--mcp-apps` (no value), `all`, or `true`	Enable every app (same as default)
`none` or `false`	Disable every app (kill-switch)
comma-separated subset, e.g. `asset-gallery,asset-details`	Enable only the listed apps

Available app names: asset-gallery, asset-details, asset-upload.

# Disable all apps

npx @cloudinary/asset-management-mcp serve --mcp-apps none

Enable only the gallery

npx @cloudinary/asset-management-mcp start --mcp-apps asset-gallery

Disable via env var

CLOUDINARY_MCP_APPS=none npx @cloudinary/asset-management-mcp start

Precedence: CLI flag > environment variable > built-in default.

Authentication

The MCP server uses your Cloudinary API key and secret for authentication:

"env": { "CLOUDINARY_CLOUD_NAME": "demo", "CLOUDINARY_API_KEY": "123456789012345", "CLOUDINARY_API_SECRET": "abcdefghijklmnopqrstuvwxyz12" } }

Available Tools

The MCP server exposes Cloudinary's Asset Management API as tools. Use your AI application to discover and invoke the available tools for uploading, managing, searching, and transforming your media assets.

Usage Examples

Example 1: Upload and Transform an Image

1. Upload a local image: "Upload file:///Users/me/photo.jpg to Cloudinary as 'hero-image'"

Transform it: "Transform asset 'hero-image' with transformations 'c_fill,w_800,h_600/e_sharpen'"
Get details: "Show me details for asset with ID [asset-id]"

Example 2: Search and Organize Assets

1. Search for images: "Find all images with tag 'product' uploaded in the last 7 days"

Create folder: "Create a new folder called 'summer-2024-products'"
List assets: "Show me all video assets in the 'marketing' folder"

Example 3: Generate Archive

1. Get transformation docs: "Show me the Cloudinary transformation reference"

Apply transformations: "Transform 'banner' asset with 'c_scale,w_1200/f_auto,q_auto'"
Create archive: "Generate a ZIP archive of all images with tag 'export-ready'"

Example 4: Asset Management Workflow

1. Upload multiple files: "Upload all images from folder /assets/new-products/"

Add tags: "Update asset [asset-id] and add tags 'featured,homepage'"
Get usage stats: "Show my Cloudinary account usage statistics"

Custom Tools

This MCP server includes two powerful custom tools:

`get-tx-reference`

Retrieves the complete Cloudinary transformation reference documentation.

When to use:

Before creating or modifying transformations
When user asks about image/video effects, resizing, cropping, filters

Example:

Use get-tx-reference to learn about available transformations

`transform-asset`

Applies transformations to existing assets using Cloudinary's explicit API.

Parameters:

publicId - The asset's public ID
transformations - Transformation string (e.g., c_fill,w_300,h_200)
resourceType - Type: image, video, or raw (default: image)
invalidate - Invalidate CDN cache (default: false)

Example:

Transform asset "sample" with transformations "c_fill,w_500,h_500/e_sepia"

Progressive Discovery

MCP servers with many tools can bloat LLM context windows, leading to increased token usage and tool confusion. Dynamic mode solves this by exposing only a small set of meta-tools that let agents progressively discover and invoke tools on demand.

To enable dynamic mode, pass the --mode dynamic flag when starting your server:

"mcpServers": { "CloudinaryAssetMgmt": { "command": "npx", "args": ["@cloudinary/asset-management-mcp", "start", "--mode", "dynamic"], // ... other server arguments } } }

In dynamic mode, the server registers only the following meta-tools instead of every individual tool:

`list_tools`: Lists all available tools with their names and descriptions.
`describe_tool_input`: Returns the input schema for one or more tools by name.
`execute_tool`: Executes a tool by name with its arguments.
`list_scopes`: Lists the scopes available on the server.

This approach significantly reduces the number of tokens sent to the LLM on each request, which is especially useful for servers with a large number of tools.

You can combine dynamic mode with scope and tool filters:

"mcpServers": { "CloudinaryAssetMgmt": {

Only the beginning is shown; read the rest in the repo

Cloudinary Asset Management

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Cloudinary Asset Management MCP Server

Summary

Table of Contents

Installation

Configuration

Environment Variables

CLOUDINARY_URL Format

Response Header Collection

Collect specific headers by exact name (comma-separated)

Mix exact names, prefix matching, and regex matching

Header matching specs

MCP Apps

Enable only the gallery

Disable via env var

Authentication

Available Tools

Usage Examples

Example 1: Upload and Transform an Image

Example 2: Search and Organize Assets

Example 3: Generate Archive

Example 4: Asset Management Workflow

Custom Tools

get-tx-reference

transform-asset

Progressive Discovery

`get-tx-reference`

`transform-asset`