# Cloudinary Structured Metadata MCP server

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

- Listing: https://mcp.tc/i/cloudinary-structured-metadata
- Connect: use the server's own URL `https://structured-metadata.mcp.cloudinary.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: Cloudinary
- Homepage: <https://cloudinary.com/documentation/cloudinary_llm_mcp>
- Docs: <https://cloudinary.com/documentation/cloudinary_llm_mcp>
- Repository: <https://github.com/cloudinary/structured-metadata-mcp>
- Package: npm `@cloudinary/structured-metadata-mcp`

## 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 it 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.

## 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."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http cloudinary-structured-metadata https://structured-metadata.mcp.cloudinary.com/mcp
```

2. 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:

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

3. 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:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Cloudinary%20Structured%20Metadata&connectorUrl=https%3A%2F%2Fstructured-metadata.mcp.cloudinary.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://structured-metadata.mcp.cloudinary.com/mcp` and click **Add**.

3. 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

[Add to Cursor](<https://cursor.com/install-mcp?name=cloudinary-structured-metadata&config=eyJ1cmwiOiJodHRwczovL3N0cnVjdHVyZWQtbWV0YWRhdGEubWNwLmNsb3VkaW5hcnkuY29tL21jcCJ9>) (opens Cursor)

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

`mcp.json`:

```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

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=cloudinary-structured-metadata&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fstructured-metadata.mcp.cloudinary.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
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`:

```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`:

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

2. 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

```bash
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`:

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

### Gemini CLI

```bash
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.

```json
{
  "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`.

## Recent changes

- 2026-11-12 23:27 UTC: Tracking started: 11 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/cloudinary-structured-metadata#history (Atom feed: https://mcp.tc/i/cloudinary-structured-metadata/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.6.2
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-12
- Updated: 2026-11-12

---
Source: https://mcp.tc/i/cloudinary-structured-metadata (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
