Box vs Cloudinary Structured Metadata
Box is an MCP server published by dgageot. Marketplaces we read that list it: 1 (Docker MCP Catalog). Cloudinary Structured Metadata is an MCP server published by cloudinary.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Box |  Cloudinary Structured Metadata |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4db7963505c2 Forks (GitHub): 0 Pulls (Docker Hub): 19 067 Stars (Docker Hub): 3 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Box | Cloudinary Structured Metadata |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Pulls (Docker Hub) (differs) | 19 067 | No figure on Docker Hub |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/box) | Remote server (structured-metadata.mcp.cloudinary.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dgageot/mcp-server-box | github.com/cloudinary/structured-metadata-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Box
An MCP server capable of interacting with the Box API.
Cloudinary Structured Metadata
Create and manage Cloudinary structured metadata fields, datasources, and rules.
How to run each
Box As a local MCP server: Docker image
claude mcp add --env "BOX_CLIENT_SECRET=<YOUR_BOX_CLIENT_SECRET>" --transport stdio box -- docker run -i --rm -e BOX_CLIENT_SECRET mcp/boxRequires: BOX_CLIENT_SECRET (secret)
Cloudinary Structured Metadata As a remote MCP server
claude mcp add --transport http structured-metadata-mcp https://structured-metadata.mcp.cloudinary.com/mcp --header "cloudinary-api-secret: <YOUR_CLOUDINARY_API_SECRET>"Requires: CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET (secret), CLOUDINARY_CLOUD_NAME, cloudinary-api-secret header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Cloudinary Structured Metadata has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Cloudinary Structured Metadata publish no list of tools, so we do not compare tools.
Settings each asks for
Only Box asks for
BOX_CLIENT_IDBOX_CLIENT_SECRET (secret)
Only Cloudinary Structured Metadata asks for
CLOUDINARY_API_KEYCLOUDINARY_API_SECRET (secret)CLOUDINARY_CLOUD_NAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Box · What it can do: Cloudinary Structured Metadata · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.