com.cloudinary/structured-metadata-mcp
Cloudinary Structured Metadata
Is the Cloudinary Structured Metadata MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Create and manage Cloudinary structured metadata fields, datasources, and rules.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Authentication required. Provide either OAuth Bearer token or API- Endpoint
- https://structured-metadata.mcp.cloudinary.com/mcp (streamable-http)
- Host
- structured-metadata.mcp.cloudinary.com
- Package
- The publisher's package npm:@cloudinary/structured-metadata-mcp did not list its tools in the container: crashed on start, MCP error -32000: Connection closed.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://structured-metadata.mcp.cloudinary.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server structured-metadata.mcp.cloudinary.com, PKCE S256, grants authorization_code, refresh_token.
Scopes openid profile email offline_access asset_management upload.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/cloudinary/structured-metadata-mcp
- Website
- https://cloudinary.com/documentation/cloudinary_llm_mcp
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention structured.
- AkkruData ai.akkrudata/akkrudata · needs auth
- Lenny Rachitsky Podcast Transcripts MCP Server ai.com.mcp/lenny-rachitsky-podcast · alive
- ai.extend/extend · needs auth
- ai.getvda/claude-schema-output-agent · newer protocol
- ai.getvda/structured-output-agent · newer protocol
- ai.getvda/structured-output-agent-c2ddcc · newer protocol
- ai.getvda/structured-output-agent-openai · newer protocol
- ai.getvda/structured-output-mcp-agent-instructor · newer protocol
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.