Cloudinary Structured Metadata

com.cloudinaryPublished by cloudinary.comOfficial publisherv0.6.2Updated Nov 13, 2026

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

The publisher's own server: Cloudinary Analysis

VerifiedStreamable HTTPWeb executableData & AnalyticsMedia & Design

Overview

AI-generated overview

Lets an assistant create and manage Cloudinary structured metadata fields, datasources and rules through Cloudinary's Structured Metadata API.

What you can do
  • List, create, get, update and delete metadata fields, including enum values and field ordering
  • Search, add, remove and restore entries in field datasources
  • List, create, update and delete metadata rules that auto-tag assets, for example by folder
  • Optionally run in a dynamic mode that exposes only meta-tools for listing, describing and executing tools to save context
When to use it
Useful when you manage a Cloudinary account and want an assistant to set up or maintain the metadata schema behind asset organization — defining fields, keeping enum datasources current, and configuring auto-tagging rules — without clicking through the dashboard.
Requirements
Either the remote endpoint or a local process via the npm package (Node.js 20.19.0 or later) or the Docker image. Requires a Cloudinary cloud name, API key and API secret, supplied as CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY and CLOUDINARY_API_SECRET, as the cloudinary-cloud-name, cloudinary-api-key and cloudinary-api-secret headers, or as a single CLOUDINARY_URL. OAuth is declared for the remote endpoint.
Before you install
The API secret grants account-level access; store CLOUDINARY_API_SECRET or the cloudinary-api-secret header securely and avoid pasting it into shared configs. Tools can create, update and delete metadata fields, datasource entries and rules, and rules change how assets are tagged, so confirm destructive or schema-changing operations before running them. Metadata operations are sent to Cloudinary's API.

Installation

In SourceWeft

  1. Open Cloudinary Structured Metadata in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.cloudinary%2Fstructured-metadata-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Source: README.md at commit a77ad79

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.6.2LatestNov 13, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Cloudinary integrations