Cloudinary Asset Management

Name: Cloudinary Asset Management
Author: cloudinary

作者：cloudinary版本 0.11.6i★ –i电脑或云端

注册名称io.github.cloudinary/asset-management-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 搜索与 AI 记忆
你需要填写：CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET, cloudinary-cloud-name, cloudinary-api-key, cloudinary-api-secret

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET, cloudinary-cloud-name, cloudinary-api-key, cloudinary-api-secret

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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'

或者在你的电脑上运行

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

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

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

服务器要求先登录，才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 cloudinary 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 269 毫秒内响应（HTTP 401）
✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录，你的 AI 应用可以带你去登录
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7254 个服务器的 0%
发布到注册中心的时间比此分类中其他 7254 个服务器的 95% 更新
基础检查结果等于或优于此分类中其他 7254 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Cloudinary Asset Management 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET, cloudinary-cloud-name, cloudinary-api-key, cloudinary-api-secret

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.11.6）于昨天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT今天更新

安装

Codebase Memory

作者：DeusData

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

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

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

在云端运行★ 5,213MIT上个月更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读

Cloudinary Asset Management

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“搜索与 AI 记忆”中的其他服务器比较i

常见问题

替代选择

Context7

Codebase Memory

Exa

作者的 README

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`