Cloudinary Asset Management
com.cloudinary由 cloudinary.com 发布官方发布者v0.11.8更新于 Nov 15, 2026
使用AI驱动的工具上传、生成、整理、搜索和转换图像、视频及文件。
AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。
原文描述
Upload, generate, organize, search, and transform images, videos, and files with AI-powered tools.
发布方自己的服务:Cloudinary Analysis
概览
Cloudinary Asset Management 的托管 MCP 服务(asset-management.mcp.cloudinary.com),由 cloudinary.com 发布;需要 OAuth 登录或 API 密钥;Streamable HTTP。
暂无 AI 概览:以下信息来自注册中心条目和服务本身。
- 发布者
- cloudinary.com
- 端点
- asset-management.mcp.cloudinary.com
- 最近检查
安装
在 SourceWeft 中
- 打开 控制台中的 Cloudinary Asset Management,将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/com.cloudinary%2Fasset-management-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"mcpServers": {
"cloudinary-asset-management": {
"type": "http",
"url": "https://asset-management.mcp.cloudinary.com/mcp"
}
}
}README
Cloudinary Asset Management MCP Server
Summary
Table of Contents
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:
Claude Code CLI
Gemini
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 configto open up the mcp configuration file. - If the configuration file is empty paste the full json
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
Stdio installation via npm
To start the MCP server, run:For a full list of server arguments, run:
Configuration
Environment Variables
The MCP server supports the following environment variables:
CLOUDINARY_URL Format
You can use a single CLOUDINARY_URL instead of individual variables:
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:
Header matching specs
Each entry in the comma-separated list is matched against response header names:
You can also set this via the CLOUDINARY_URL query parameter:
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:
Available app names: asset-gallery, asset-details, asset-upload.
Precedence: CLI flag > environment variable > built-in default.
Authentication
The MCP server uses your Cloudinary API key and secret for authentication:
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, transforming, and generating your media assets.
- Assets: upload, inspect, update, rename, and delete images, videos, and raw files
- Tags and metadata: tag assets, set contextual and structured metadata, and relate assets to each other
- Search: find assets by tags, folder, format, metadata, and dates, or by visual similarity
- Folders: create, move, and delete folders in the media library
- Transformations: create and remove derived versions: resize, crop, change format, apply effects
- Image generation: create an image from a text prompt, or edit and combine existing images with a prompt
- Video generation (Beta): animate an image from your account into a short video with a prompt
- Collections: group assets into collections without moving them, and share a collection on a public page
- Archives and usage: package assets as ZIP or TGZ files, and check account usage
Usage Examples
Example 1: Upload and Transform an Image
Example 2: Generate and Edit Images
Example 3: Generate a Video from an Image
Example 4: Search and Organize Assets
Example 5: Build and Share a Collection
Example 6: Asset Management Workflow
Example 7: Generate Archive
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:
transform-asset
Applies transformations to existing assets using Cloudinary's explicit API.
Parameters:
publicId- The asset's public IDtransformations- Transformation string (e.g.,c_fill,w_300,h_200)resourceType- Type:image,video, orraw(default:image)invalidate- Invalidate CDN cache (default:false)
Example:
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:
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:
Development
Building from Source
Prerequisites
- Node.js v20 or higher
- npm, pnpm, bun, or yarn
Build Steps
Project Structure
Contributions
While we value contributions to this MCP Server, most of the code is generated programmatically from the Cloudinary API spec. Any manual changes to generated files will be overwritten on the next generation — please direct your changes to the manual extension points below.
What you can contribute:
- Custom tools and server wiring in
src/mcp-server/server.extensions.ts - MCP UI Apps in
src/mcp-server/apps/(gallery, details, upload, and new apps) - SDK hooks in
src/hooks/(auth, custom headers, response headers, user agent) - Documentation improvements (this README, JSDoc on manual files)
- Bug reports and feature requests
Generated files (do not edit):
src/mcp-server/server.tssrc/mcp-server/tools/*.tssrc/funcs/*.tssrc/models/*.ts
When touching generated files is unavoidable, prefer updating the upstream spec or Speakeasy configuration in .speakeasy/ so the change survives regeneration.
We look forward to hearing your feedback. Feel free to open a PR or issue with a proof of concept and we'll do our best to include it in a future release.
MCP Server Created by Speakeasy
来源:README.md,提交 177d9ab
工具
0版本历史
2- v0.11.8最新Nov 15, 2026
- v0.11.7Nov 13, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Cloudinary 集成
Cloudinary Analysis
com.cloudinary官方发布者
Cloudinary Analysis MCP 服务器让助手对图片执行 AI 分析,包括内容审核、生成说明、打标签、画质与水印检测。
Cloudinary Structured Metadata
com.cloudinary官方发布者
让助手通过 Cloudinary 结构化元数据 API 创建和管理元数据字段、数据源与规则。
Cloudinary Environment Config
com.cloudinary官方发布者
将 AI 助手连接到 Cloudinary 账户,管理命名转换、上传预设、流媒体配置、Webhook 触发器和上传映射。

Cldsh Cloudinary Shell
由 GitHub 账号 Sheldon1999 发布
集 MCP 服务器、Shell 与 CLI 于一体,让助手像操作文件系统一样浏览、上传、移动、下载和删除 Cloudinary 账户中的资源。

Cloudinary Asset Management
由 GitHub 账号 subomi 发布
一个本地 MCP 服务器,让助手在 Cloudinary 账户中上传、整理、搜索和转换图片、视频与文件。