Cloudinary Asset Management

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "cloudinary-asset-management": {
      "command": "npx",
      "args": [
        "-y",
        "cloudinary-asset-management"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Cloudinary Asset Management MCP Server

Summary

Cloudinary Asset Management MCP Server
Development
- Building from Source
- Contributions

Installation

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:

config.json

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

Claude Code CLI

Terminal

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

Gemini

bash

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

JSON Config

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

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

JSON Config

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

Stdio installation via npm

To start the MCP server, run:

Terminal

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

For a full list of server arguments, run:

Terminal

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:

bash

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:

bash

# 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:<value>`	`prefix:x-featureratelimit-`	matches any header starting with `x-featureratelimit-`
`regex:<pattern>`	`regex:ratelimit`	matches any header whose name contains `ratelimit`

You can also set this via the CLOUDINARY_URL query parameter:

bash

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.

bash

# 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:

config.json

{
  "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

yaml

1. Upload a local image: "Upload file:///Users/me/photo.jpg to Cloudinary as 'hero-image'"
2. Transform it: "Transform asset 'hero-image' with transformations 'c_fill,w_800,h_600/e_sharpen'"
3. Get details: "Show me details for asset with ID [asset-id]"

Example 2: Search and Organize Assets

yaml

1. Search for images: "Find all images with tag 'product' uploaded in the last 7 days"
2. Create folder: "Create a new folder called 'summer-2024-products'"
3. List assets: "Show me all video assets in the 'marketing' folder"

Example 3: Generate Archive

yaml

1. Get transformation docs: "Show me the Cloudinary transformation reference"
2. Apply transformations: "Transform 'banner' asset with 'c_scale,w_1200/f_auto,q_auto'"
3. Create archive: "Generate a ZIP archive of all images with tag 'export-ready'"

Example 4: Asset Management Workflow

yaml

1. Upload multiple files: "Upload all images from folder /assets/new-products/"
2. Add tags: "Update asset [asset-id] and add tags 'featured,homepage'"
3. 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:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Cloudinary Asset Management

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "cloudinary-asset-management": { "command": "npx", "args": ["-y", "Cloudinary Asset Management"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Cloudinary Asset Management AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/cloudinary-asset-management?style=directory)](https://allmcps.com/mcp/cloudinary-asset-management)

HTML Embed

<a href="https://allmcps.com/mcp/cloudinary-asset-management"><img src="https://allmcps.com/api/badge/cloudinary-asset-management?style=directory" alt="Cloudinary Asset Management on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Cloudinary Asset Management →Install in Claude Desktop Install in Cursor Install in VS Code

Cloudinary Asset Management

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "cloudinary-asset-management": {
      "command": "npx",
      "args": [
        "-y",
        "cloudinary-asset-management"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Cloudinary Asset Management MCP Server

Summary

Cloudinary Asset Management MCP Server
Development
- Building from Source
- Contributions

Installation

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:

config.json

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

Claude Code CLI

Terminal

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

Gemini

bash

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

JSON Config

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

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

JSON Config

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

Stdio installation via npm

To start the MCP server, run:

Terminal

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

For a full list of server arguments, run:

Terminal

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:

bash

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:

bash

# 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:<value>`	`prefix:x-featureratelimit-`	matches any header starting with `x-featureratelimit-`
`regex:<pattern>`	`regex:ratelimit`	matches any header whose name contains `ratelimit`

You can also set this via the CLOUDINARY_URL query parameter:

bash

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

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.

bash

# 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:

config.json

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

Available Tools

Usage Examples

Example 1: Upload and Transform an Image

yaml

1. Upload a local image: "Upload file:///Users/me/photo.jpg to Cloudinary as 'hero-image'"
2. Transform it: "Transform asset 'hero-image' with transformations 'c_fill,w_800,h_600/e_sharpen'"
3. Get details: "Show me details for asset with ID [asset-id]"

Example 2: Search and Organize Assets

yaml

1. Search for images: "Find all images with tag 'product' uploaded in the last 7 days"
2. Create folder: "Create a new folder called 'summer-2024-products'"
3. List assets: "Show me all video assets in the 'marketing' folder"

Example 3: Generate Archive

yaml

1. Get transformation docs: "Show me the Cloudinary transformation reference"
2. Apply transformations: "Transform 'banner' asset with 'c_scale,w_1200/f_auto,q_auto'"
3. Create archive: "Generate a ZIP archive of all images with tag 'export-ready'"

Example 4: Asset Management Workflow

yaml

1. Upload multiple files: "Upload all images from folder /assets/new-products/"
2. Add tags: "Update asset [asset-id] and add tags 'featured,homepage'"
3. 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:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Cloudinary Asset Management

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "cloudinary-asset-management": { "command": "npx", "args": ["-y", "Cloudinary Asset Management"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/cloudinary-asset-management?style=directory)](https://allmcps.com/mcp/cloudinary-asset-management)

HTML Embed

<a href="https://allmcps.com/mcp/cloudinary-asset-management"><img src="https://allmcps.com/api/badge/cloudinary-asset-management?style=directory" alt="Cloudinary Asset Management on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Cloudinary Asset Management →Install in Claude Desktop Install in Cursor Install in VS Code

Cloudinary Asset Management

Quick Install

Client Config & Setup

Documentation Overview

Cloudinary Asset Management MCP Server

Summary

Table of Contents

Installation

Configuration

Environment Variables

CLOUDINARY_URL Format

Response Header Collection

Header matching specs

MCP Apps

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

Related MCP Servers

Reviews

Frequently Asked Questions about Cloudinary Asset Management

AllMCPs Directory Badge

Technical Specs & Signals

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

Cloudinary Asset Management

Quick Install

Client Config & Setup

Documentation Overview

Cloudinary Asset Management MCP Server

Summary

Table of Contents

Installation

Configuration

Environment Variables

CLOUDINARY_URL Format

Response Header Collection

Header matching specs

MCP Apps

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

Related MCP Servers

Reviews

Frequently Asked Questions about Cloudinary Asset Management

AllMCPs Directory Badge

Technical Specs & Signals

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

`get-tx-reference`

`get-tx-reference`