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 集成