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
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.
Installation
In SourceWeft
- Open Cloudinary Structured Metadata in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.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
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:
Authentication
The MCP server uses your Cloudinary API key and secret for authentication:
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
Example 2: Manage Field Datasources
Example 3: Manage Metadata Rules
Example 4: Reorder Metadata Fields
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, 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:
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:
Source: README.md at commit a77ad79
Tools
0Version history
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
Cloudinary Analysis
com.cloudinaryOfficial publisher
Cloudinary Analysis MCP server lets an assistant run AI-powered analysis on images: moderation, captioning, tagging, quality and watermark checks.
Cloudinary Environment Config
com.cloudinaryOfficial publisher
Connects an AI assistant to a Cloudinary account to manage named transformations, upload presets, streaming profiles, webhook triggers and upload mappings.
Cloudinary Asset Management
com.cloudinaryOfficial publisher
Cloudinary Asset Management's hosted MCP server, published by cloudinary.com; credential required; Streamable HTTP.

Cldsh Cloudinary Shell
Published by GitHub account Sheldon1999
MCP server, shell and CLI that lets an assistant browse, upload, move, download and delete assets in a Cloudinary account like a file system.

Cloudinary Asset Management
Published by GitHub account subomi
A local MCP server that lets an assistant upload, organize, search and transform images, videos and files in a Cloudinary account.