
Cloudinary Asset Management
io.github.cloudinary由 GitHub 帳號 cloudinary 發布v0.11.6更新於 Nov 19, 2026
Upload, generate, organize, search, and transform images, videos, and files with AI-powered tools.
發布方自己的服務:Cloudinary Analysis
概覽
Cloudinary 資產管理讓助手在 Cloudinary 帳戶中上傳、搜尋、整理、轉換與生成圖片、影片和檔案。
- 可以做什麼
- 上傳、檢視、更新、重新命名與刪除圖片、影片及原始檔案
- 為素材加上標籤,設定情境與結構化中繼資料,並建立素材之間的關聯
- 依標籤、資料夾、格式、中繼資料、日期或視覺相似度搜尋;建立、移動與刪除資料夾
- 透過縮放、裁切、格式轉換與特效建立或移除衍生版本
- 依提示詞生成圖片、編輯既有圖片,並把圖片製作成短影片(測試版)
- 將素材歸入可分享的合集,打包成 ZIP 或 TGZ 封存檔,並查看帳戶用量
- 適用情境
- 適合媒體素材存放在 Cloudinary,且希望助手在對話中直接尋找、清理、標記、轉換或生成素材的情況。也適用於需要批次上傳、資料夾整理、可分享合集或封存檔的行銷與商品目錄流程。
- 執行需求
- 可使用遠端端點,或透過 npm(需 Node.js 20.19.0 以上)或 Docker 在本機執行。需要 Cloudinary 雲端名稱以及 API key 與 API secret,可透過 CLOUDINARY_CLOUD_NAME、CLOUDINARY_API_KEY、CLOUDINARY_API_SECRET,或 cloudinary-* 標頭,或單一 CLOUDINARY_URL 提供。遠端端點宣告使用 OAuth。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Cloudinary Asset Management,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.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版本歷史
3- v0.11.6最新Nov 5, 2026
- v0.11.5Oct 23, 2026
- v0.8.1Sep 16, 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 觸發條件與上傳對應。
Cloudinary Asset Management
com.cloudinary官方發布者
使用AI驅動的工具上傳、產生、整理、搜尋和轉換影像、影片及檔案。AI 翻譯

Cldsh Cloudinary Shell
由 GitHub 帳號 Sheldon1999 發布
結合 MCP 伺服器、Shell 與 CLI,讓助手像操作檔案系統一樣瀏覽、上傳、移動、下載和刪除 Cloudinary 帳戶中的資源。