Cloudinary Structured Metadata

com.cloudinary由 cloudinary.com 發布官方發布者v0.6.2更新於 Nov 13, 2026

Create and manage Cloudinary structured metadata fields, datasources, and rules.

發布方自己的服務:Cloudinary Analysis

已驗證Streamable HTTP可網頁執行資料與分析媒體與設計

概覽

AI 產生的概覽

讓助理透過 Cloudinary 結構化中繼資料 API 建立與管理中繼資料欄位、資料來源和規則。

可以做什麼
  • 列出、建立、檢視、更新與刪除中繼資料欄位,包含列舉值與欄位排序
  • 搜尋、新增、移除與還原欄位資料來源中的項目
  • 列出、建立、更新與刪除中繼資料規則,例如依資料夾自動標記
  • 可選擇啟用動態模式,只暴露用來列出、描述與執行工具的元工具,以節省上下文
適用情境
適合需要管理 Cloudinary 帳戶、想讓助理建立或維護資產整理所需中繼資料結構的情況,例如定義欄位、維護列舉資料來源、設定自動標記規則,而不必在控制台中逐項操作。
執行需求
可使用遠端端點,或透過 npm 套件(需 Node.js 20.19.0 以上)或 Docker 映像在本機執行。需要 Cloudinary 雲端名稱、API key 與 API secret,可透過 CLOUDINARY_CLOUD_NAME、CLOUDINARY_API_KEY、CLOUDINARY_API_SECRET 環境變數,或 cloudinary-cloud-name、cloudinary-api-key、cloudinary-api-secret 標頭,或單一 CLOUDINARY_URL 提供。遠端端點宣告使用 OAuth。
安裝前請注意
API secret 具備帳戶層級權限,請妥善保管 CLOUDINARY_API_SECRET 或 cloudinary-api-secret 標頭,不要寫入共用設定。工具可建立、更新與刪除中繼資料欄位、資料來源項目和規則,且規則會改變資產的標記方式,執行破壞性或變更結構的操作前應先確認。中繼資料操作會傳送至 Cloudinary 的 API。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Cloudinary Structured Metadata,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.cloudinary%2Fstructured-metadata-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "cloudinary-structured-metadata": {
      "type": "http",
      "url": "https://structured-metadata.mcp.cloudinary.com/mcp"
    }
  }
}

README

Cloudinary Structured Metadata 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

[Install MCP Server]

Or manually:

  1. Open Cursor Settings
  2. Select Tools and Integrations
  3. Select New MCP Server
  4. If the configuration file is empty paste the following JSON into the MCP Server Configuration:
json
{  "command": "npx",  "args": [    "@cloudinary/structured-metadata-mcp",    "start",    "--api-key",    "",    "--api-secret",    "",    "--cloud-name",    ""  ]}
Claude Code CLI
bash
claude mcp add CloudinarySMD -- npx -y @cloudinary/structured-metadata-mcp start --api-key  --api-secret  --cloud-name 
Gemini
bash
gemini mcp add CloudinarySMD -- npx -y @cloudinary/structured-metadata-mcp start --api-key  --api-secret  --cloud-name 
Windsurf

Refer to Official Windsurf documentation for latest information

  1. Open Windsurf Settings
  2. Select Cascade on left side menu
  3. Click on Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)
  4. Click on View raw config to open up the mcp configuration file.
  5. If the configuration file is empty paste the full json
bash
{  "command": "npx",  "args": [    "@cloudinary/structured-metadata-mcp",    "start",    "--api-key",    "",    "--api-secret",    "",    "--cloud-name",    ""  ]}
VS Code

[Install in VS Code]

Or manually:

Refer to Official VS Code documentation for latest information

  1. Open Command Palette
  2. Search and open MCP: Open User Configuration. This should open mcp.json file
  3. If the configuration file is empty paste the full json
bash
{  "command": "npx",  "args": [    "@cloudinary/structured-metadata-mcp",    "start",    "--api-key",    "",    "--api-secret",    "",    "--cloud-name",    ""  ]}
Stdio installation via npm To start the MCP server, run:
bash
npx @cloudinary/structured-metadata-mcp start --api-key  --api-secret  --cloud-name 

For a full list of server arguments, run:

npx @cloudinary/structured-metadata-mcp --help

Configuration

Environment Variables

The MCP server supports the following environment variables:

VariableDescriptionRequired
CLOUDINARY_CLOUD_NAMEYour Cloudinary cloud nameYes
CLOUDINARY_API_KEYYour Cloudinary API keyYes
CLOUDINARY_API_SECRETYour Cloudinary API secretYes
CLOUDINARY_URLComplete Cloudinary URL (alternative to individual vars)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

Authentication

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

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

Available Tools

The MCP server exposes Cloudinary's Structured Metadata API as tools. Use your AI application to discover and invoke the available tools for managing metadata fields and rules.

Usage Examples

Example 1: Manage Metadata Fields
1. List fields: "Show me all metadata fields in my account"2. Create field: "Create a metadata field named 'category' of type 'enum' with values 'product,service,other'"3. Get field: "Get details for the metadata field 'category'"4. Update field: "Update the 'category' field to add a new value 'subscription'"5. Delete field: "Delete the metadata field 'old_field'"
Example 2: Manage Field Datasources
1. Search datasource: "Search for values in the 'category' field datasource"2. Update datasource: "Add a new value 'enterprise' to the 'category' field datasource"3. Delete datasource entry: "Remove the value 'old_value' from the 'category' field"4. Restore datasource: "Restore a deleted datasource entry for field 'category'"
Example 3: Manage Metadata Rules
1. List rules: "Show all metadata rules configured in my account"2. Create rule: "Create a metadata rule to auto-tag assets in folder 'products' with category 'product'"3. Update rule: "Update metadata rule [rule-id] to change the target folder"4. Delete rule: "Delete metadata rule [rule-id]"
Example 4: Reorder Metadata Fields
1. Reorder single field: "Move the 'priority' metadata field to position 2"2. Reorder multiple fields: "Reorder metadata fields: set 'category' to position 1, 'priority' to position 2"

Development

Building from Source

Prerequisites

  • Node.js v20 or higher
  • npm, pnpm, bun, or yarn

Build Steps

bash
# Clone the repositorygit clone https://github.com/cloudinary/structured-metadata-mcp.gitcd structured-metadata-mcp
# Install dependenciesnpm install
# Build the projectnpm run build
# Run locallynpm start

Project Structure

structured-metadata-mcp/├── src/│   ├── hooks/              # Custom authentication hooks│   ├── mcp-server/         # MCP server implementation│   │   ├── server.ts       # Main server (auto-generated)│   │   └── tools/          # Generated tool wrappers│   ├── funcs/              # API function implementations│   └── models/             # Type definitions├── .github/│   └── workflows/          # CI/CD workflows└── .speakeasy/             # Speakeasy configuration

Contributions

While we value contributions to this MCP Server, the code is generated programmatically. Any manual changes to generated files will be overwritten on the next generation.

What you can contribute:

  • ✅ Custom hooks in src/hooks/
  • ✅ Documentation improvements
  • ✅ Bug reports and feature requests

Generated files (do not edit):

  • ❌ src/mcp-server/server.ts
  • ❌ src/mcp-server/tools/*.ts
  • ❌ src/funcs/*.ts
  • ❌ src/models/*.ts

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

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:

jsonc
{  "mcpServers": {    "CloudinarySMD": {      "command": "npx",      "args": ["@cloudinary/structured-metadata-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:

jsonc
{  "mcpServers": {    "CloudinarySMD": {      "command": "npx",      "args": ["@cloudinary/structured-metadata-mcp", "start", "--mode", "dynamic", "--scope", "admin"],      // ... other server arguments    }  }}

來源:README.md,提交 a77ad79

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v0.6.2最新Nov 13, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Cloudinary 整合