Which integrations are available for this server?

Provides tools for interacting with Cloudinary's Structured Metadata API, enabling management of metadata fields, field datasources, metadata rules, and field ordering.

How do I use Cloudinary Structured Metadata MCP Server?

This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions: * Cloudinary Structured Metadata

Cloudinary Structured Metadata MCP Server

Official

by cloudinary

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Cloudinary Structured Metadata MCP Server

Summary

Related MCP server: Alma Atlas

Installation

The MCP server requires Node.js 20.19.0 or later.

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 aboutDesktop Extensions.

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:

{
  "command": "npx",
  "args": [
    "@cloudinary/structured-metadata-mcp",
    "start",
    "--api-key",
    "",
    "--api-secret",
    "",
    "--cloud-name",
    ""
  ]
}

claude mcp add CloudinarySMD -- npx -y @cloudinary/structured-metadata-mcp start --api-key  --api-secret  --cloud-name

gemini mcp add CloudinarySMD -- npx -y @cloudinary/structured-metadata-mcp start --api-key  --api-secret  --cloud-name

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 config to open up the mcp configuration file.
If the configuration file is empty paste the full json

{
  "command": "npx",
  "args": [
    "@cloudinary/structured-metadata-mcp",
    "start",
    "--api-key",
    "",
    "--api-secret",
    "",
    "--cloud-name",
    ""
  ]
}

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

{
  "command": "npx",
  "args": [
    "@cloudinary/structured-metadata-mcp",
    "start",
    "--api-key",
    "",
    "--api-secret",
    "",
    "--cloud-name",
    ""
  ]
}

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:

Variable	Description	Required
`CLOUDINARY_CLOUD_NAME`	Your Cloudinary cloud name	Yes
`CLOUDINARY_API_KEY`	Your Cloudinary API key	Yes
`CLOUDINARY_API_SECRET`	Your Cloudinary API secret	Yes
`CLOUDINARY_URL`	Complete Cloudinary URL (alternative to individual vars)	No

CLOUDINARY_URL Format

You can use a single CLOUDINARY_URL instead of individual variables:

CLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME

Authentication

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

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

# Clone the repository
git clone https://github.com/cloudinary/structured-metadata-mcp.git
cd structured-metadata-mcp

# Install dependencies
npm install

# Build the project
npm run build

# Run locally
npm 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:

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

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessLimited data

Resources

Related MCP Connectors

mcp-knowledgeC
io.github.getgapup
100+ MCP tools for AI agents: content metadata, trade intelligence, business-expertise analysis.
Knowledge & Memory Research & Data RAG Systems
2792
https://mcp.gapup.io
Chrysai
com.chrysai.www
Hosted MCP server for AI-driven data ops. Create apps, manage schemas, and CRUD structured data.
Data Platforms Developer Tools App Automation
2
https://www.chrysai.com/api/mcp
SRG+
io.github.srgplus
Manage SRG+ hubs, channels, content, assets, users, and workspaces from any MCP-aware AI agent.
Content Management Systems Workplace & Productivity
2
https://mcp.srgplus.com/mcp
LiveContext
ai.livecontext
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Agent Orchestration App Automation Data Platforms
1
https://livecontext.ai/mcp

Related MCP Servers

mdm-mcp
Databases Data Platforms
767560479
F
license
Not graded
quality
D
maintenance
Provides 12 MCP tools to directly interact with DEM MDM backend API, enabling Cursor or AI agents to manage MDM data.
Updated 2 months ago (2026-09-10 02:45 UTC)
-
Alma Atlas
Databases Data Platforms Knowledge & Memory
velum-labs
A
license
Not graded
quality
D
maintenance
Enables AI agents to query live schema, lineage, and query-context across data warehouses, dbt projects, orchestration systems, and BI tools via MCP tools.
Updated 7 months ago (2026-04-27 22:42 UTC)
Apache 2.0
Iconik MCP Server
Content Management Systems Search Multimedia Processing
postforward
A
license
C
quality
B
maintenance
Enables AI assistants to interact with your Iconik media asset management library, providing 143 MCP tools for search, metadata, collections, and more.
Updated 10 days ago (2026-11-02 16:30 UTC)
85
ISC
mendix-mcp-server
Developer Tools Cloud Platforms
dhanavel-013
A
license
Not graded
quality
D
maintenance
Enables AI agents to read and modify Mendix application models through MCP tools for creating modules, entities, pages, microflows, deploying, and querying runtime data.
Updated 4 months ago (2026-07-07 06:10 UTC)
1
ISC

Cloudinary Structured Metadata MCP Server

Summary

Table of Contents

Installation

Configuration

Environment Variables

CLOUDINARY_URL Format

Authentication

Available Tools

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

Build Steps

Project Structure

Contributions

MCP Server Created by Speakeasy

Progressive Discovery

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

mdm-mcp

Alma Atlas

Iconik MCP Server

mendix-mcp-server