We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Cloudinary Structured Metadata

MCP server by Cloudinary

Create and manage Cloudinary structured metadata fields, datasource values and conditional metadata rules.

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to Cloudinary Structured Metadata

Cloudinary Structured Metadata needs sign-in. Connect with its own URL:

https://structured-metadata.mcp.cloudinary.com/mcp

Your client opens Cloudinary’s sign-in the first time you use it. The token stays between your client and Cloudinary.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/cloudinary-structured-metadata

About

Connects to the Cloudinary Structured Metadata API so an assistant can list, create, update and delete metadata fields, edit the allowed values of a field's datasource, and manage conditional metadata rules in a product environment.

It runs as a hosted remote endpoint over streamable HTTP, or locally through the npm package @cloudinary/structured-metadata-mcp (Node.js 20.19 or later). The hosted endpoint uses OAuth sign-in to Cloudinary, where you pick the product environment. API key authentication via headers is also supported, using your cloud name, API key and API secret.

What you can do

  • List, create, get, update and delete structured metadata fields
  • Update or remove allowed values in a field's datasource
  • Create, list, update and delete conditional metadata rules
  • Sign in with OAuth or use API key headers

Tools 11

  • create-metadata-field

    Create a new structured metadata field with the given properties.

  • list-metadata-fields

    List metadata fields in the product environment, with optional filters.

  • get-metadata-field

    Get the definition of a metadata field by its external_id.

  • update-metadata-field

    Update the configuration of an existing metadata field.

  • delete-metadata-field

    Permanently delete a metadata field definition.

  • update-metadata-datasource-values

    Add, modify or reorder allowed values in a field's datasource.

  • delete-metadata-datasource-values

    Remove allowed values from a field's datasource by external ID.

  • create-metadata-rule

    Create a new conditional metadata rule.

  • list-metadata-rules

    List all conditional metadata rules in the account.

  • update-metadata-rule

    Update an existing conditional metadata rule.

  • delete-metadata-rule

    Permanently delete a conditional metadata rule by ID.

From the package’s own manifest, not a live connection, on 18 Nov 2026.

Example prompts

  • Show me all structured metadata fields in my Cloudinary account.

  • Create an enum metadata field named category with values product, service and other.

  • Add the value enterprise to the category field's datasource.

  • List all conditional metadata rules and delete the one with a given ID.

Set up

Every client connects to structured-metadata.mcp.cloudinary.com, and Cloudinary asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http cloudinary-structured-metadata https://structured-metadata.mcp.cloudinary.com/mcp
  1. Start Claude Code, type /mcp, pick cloudinary-structured-metadata and choose Authenticate. A browser window opens for the Cloudinary sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it Cloudinary Structured Metadata and paste this URL:
https://structured-metadata.mcp.cloudinary.com/mcp
  1. Click Add, then Connect, and sign in when Cloudinary asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://structured-metadata.mcp.cloudinary.com/mcp and click Add.
  2. Click Connect and sign in when Cloudinary asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://structured-metadata.mcp.cloudinary.com/mcp as the server URL, then for authentication choose OAuth. ChatGPT sends you to Cloudinary to sign in.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "cloudinary-structured-metadata": {
      "url": "https://structured-metadata.mcp.cloudinary.com/mcp"
    }
  }
}

Cursor shows Needs authentication next to the server. Click the button beside it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"cloudinary-structured-metadata","type":"http","url":"https://structured-metadata.mcp.cloudinary.com/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "cloudinary-structured-metadata": {
      "type": "http",
      "url": "https://structured-metadata.mcp.cloudinary.com/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "cloudinary-structured-metadata": {
      "serverUrl": "https://structured-metadata.mcp.cloudinary.com/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add cloudinary-structured-metadata --url https://structured-metadata.mcp.cloudinary.com/mcp
codex mcp login cloudinary-structured-metadata

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.cloudinary-structured-metadata]
url = "https://structured-metadata.mcp.cloudinary.com/mcp"

Gemini CLI

gemini mcp add --transport http cloudinary-structured-metadata https://structured-metadata.mcp.cloudinary.com/mcp

Then, inside Gemini CLI, run /mcp auth cloudinary-structured-metadata to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "cloudinary-structured-metadata": {
      "type": "http",
      "url": "https://structured-metadata.mcp.cloudinary.com/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://structured-metadata.mcp.cloudinary.com/mcp.

Embed

Show Cloudinary Structured Metadata in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Cloudinary Structured Metadata on mcp.tc](https://mcp.tc/i/cloudinary-structured-metadata/badge.svg)](https://mcp.tc/i/cloudinary-structured-metadata)
HTML
<a href="https://mcp.tc/i/cloudinary-structured-metadata"><img src="https://mcp.tc/i/cloudinary-structured-metadata/badge.svg" alt="Cloudinary Structured Metadata on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/cloudinary-structured-metadata.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/cloudinary-structured-metadata" title="Cloudinary Structured Metadata on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/cloudinary-structured-metadata.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Cloudinary Structured Metadata card to your site.

Markdown
Add the mcp.tc card for Cloudinary Structured Metadata, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/cloudinary-structured-metadata.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="cloudinary-structured-metadata"><a href="https://mcp.tc/i/cloudinary-structured-metadata">Cloudinary Structured Metadata on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Cloudinary Structured Metadata on mcp.tc](https://mcp.tc/i/cloudinary-structured-metadata/badge.svg)](https://mcp.tc/i/cloudinary-structured-metadata)
```

Reference: https://mcp.tc/embed

Change history

We read the tool list in this server’s bundle manifest on GitHub every 3 hours and record what changes. Last read 18 Nov 2026, 05:28 UTC.

Follow Cloudinary Structured Metadata and we’ll email you when something changes.

  1. , Automatic check

    Tracking started: 11 tools.

FAQ

Can I paste mcp.tc/i/cloudinary-structured-metadata into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://structured-metadata.mcp.cloudinary.com/mcp, so your client talks to Cloudinary Structured Metadata directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Cloudinary Structured Metadata need an API key or a sign-in?

Yes, you need a Cloudinary account. The first time your client connects, it opens Cloudinary’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is Cloudinary Structured Metadata a remote or a local server?

Remote. Cloudinary hosts it at https://structured-metadata.mcp.cloudinary.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Cloudinary Structured Metadata do?

It has 11 tools, including create-metadata-field, list-metadata-fields and get-metadata-field. You can list, create, get, update and delete structured metadata fields, update or remove allowed values in a field's datasource and create, list, update and delete conditional metadata rules.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to Cloudinary Structured Metadata?

Yes. We follow the tool list in Cloudinary Structured Metadata’s bundle manifest, and its History tab shows each change we find, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Cloudinary Structured Metadata’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Cloudinary. This page was built from Cloudinary Structured Metadata’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.