Cloudinary Structured Metadata — Claude Code MCP server: install
This MCP server for Claude Code manages Cloudinary structured metadata. It comes into play when an agent needs to work with metadata fields, their value sources, or rules.
MIT updated 2026-11-16
claude mcp add --transport http structured-metadata-mcp https://structured-metadata.mcp.cloudinary.com/mcpWhat Cloudinary Structured Metadata does
The server gives an agent tools for Cloudinary’s Structured Metadata API. It can list, create, edit, and delete metadata fields and rules, as well as search field value sources and restore removed entries.
Access requires a Cloudinary cloud name, API key, and API secret; CLOUDINARY_URL can replace the separate credentials. Local execution requires Node.js 20.19.0 or later. Claude Code can connect over HTTP or launch the package through npx using stdio.
What it helps with
- list metadata fields in a Cloudinary account
- create a field with a set of allowed values
- change values in a field’s datasource
- set a rule to tag assets in a folder
Example prompts for the agent
- Show the metadata fields in my Cloudinary account.
- Add
enterpriseto the datasource forcategory. - Create a rule that assigns category
productto assets in theproductsfolder.
How to install Cloudinary Structured Metadata
1Platform CLI: remote server
claude mcp add --transport http structured-metadata-mcp https://structured-metadata.mcp.cloudinary.com/mcp2Platform CLI
claude mcp add --env CLOUDINARY_CLOUD_NAME=<CLOUDINARY_CLOUD_NAME> --env CLOUDINARY_API_KEY=<CLOUDINARY_API_KEY> --env CLOUDINARY_API_SECRET=<CLOUDINARY_API_SECRET> --transport stdio cloudinary-structured-metadata -- npx -y @cloudinary/structured-metadata-mcpReplace <…> with your own values
1Platform CLI: remote server
codex mcp add cloudinary-structured-metadata --url https://structured-metadata.mcp.cloudinary.com/mcp2Platform CLI
codex mcp add cloudinary-structured-metadata --env CLOUDINARY_CLOUD_NAME=<CLOUDINARY_CLOUD_NAME> --env CLOUDINARY_API_KEY=<CLOUDINARY_API_KEY> --env CLOUDINARY_API_SECRET=<CLOUDINARY_API_SECRET> -- npx -y @cloudinary/structured-metadata-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"cloudinary-structured-metadata": {
"url": "https://structured-metadata.mcp.cloudinary.com/mcp"
}
}
}{
"mcpServers": {
"cloudinary-structured-metadata": {
"command": "npx",
"args": [
"-y",
"@cloudinary/structured-metadata-mcp"
],
"env": {
"CLOUDINARY_CLOUD_NAME": "<CLOUDINARY_CLOUD_NAME>",
"CLOUDINARY_API_KEY": "<CLOUDINARY_API_KEY>",
"CLOUDINARY_API_SECRET": "<CLOUDINARY_API_SECRET>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"cloudinary-structured-metadata": {
"type": "http",
"url": "https://structured-metadata.mcp.cloudinary.com/mcp"
}
}
}{
"servers": {
"cloudinary-structured-metadata": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cloudinary/structured-metadata-mcp"
],
"env": {
"CLOUDINARY_CLOUD_NAME": "<CLOUDINARY_CLOUD_NAME>",
"CLOUDINARY_API_KEY": "<CLOUDINARY_API_KEY>",
"CLOUDINARY_API_SECRET": "<CLOUDINARY_API_SECRET>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http cloudinary-structured-metadata https://structured-metadata.mcp.cloudinary.com/mcp2Platform CLI
gemini mcp add -e CLOUDINARY_CLOUD_NAME=<CLOUDINARY_CLOUD_NAME> -e CLOUDINARY_API_KEY=<CLOUDINARY_API_KEY> -e CLOUDINARY_API_SECRET=<CLOUDINARY_API_SECRET> cloudinary-structured-metadata npx -y @cloudinary/structured-metadata-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Cloudinary Structured Metadata
How do I install Cloudinary Structured Metadata in Claude Code?
For an HTTP connection, run claude mcp add --transport http structured-metadata-mcp https://structured-metadata.mcp.cloudinary.com/mcp.
What does Cloudinary Structured Metadata do?
It exposes tools for managing Cloudinary structured metadata fields, their value sources, and rules.
What does Cloudinary Structured Metadata need to run?
It needs a Cloudinary cloud name, API key, and API secret. Local execution also requires Node.js 20.19.0 or later; CLOUDINARY_URL can hold the credentials instead.