01 · Records and state owned
Media assets, folders, tags, derived assets, structured metadata, product-environment configuration, moderation/analysis results, and MediaFlows automation context.
Cloudinary
Cloudinary
A major API-first image and video platform whose transformation, asset-management, delivery, and event capabilities are particularly well suited to custom production surfaces.
Media generation, video & localizationSystem of productionExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Search and inspect assets, folders, tags, transformations and derived media, structured metadata, environment configuration, analysis or moderation results, and MediaFlows state.
03 · Actions and write paths
Upload, transform, rename, delete, organize, tag, configure presets/mappings/webhooks, manage metadata definitions, run analyses, and create/manage MediaFlows automations.
04 · Authentication and permissions
Remote servers default to OAuth and product-environment selection; most also accept API credentials. Local servers require managed credentials, and optional headers can restrict region and tools.
05 · Monitoring, approval, and recovery
Enable only required servers and tools, select the intended product environment and region, and review asset deletion or rename, configuration, metadata, moderation, and MediaFlows changes.
06 · Limits and caveats
Streamable HTTP `/mcp` is recommended; `/sse` is deprecated except for Analysis. Analysis currently requires OAuth and does not support API-key authentication.
Agent access
MCP support
Official MCP serverCloudinary portfolio of first-party MCP serversCurrent documented services
Support: Official MCP server
Read scope: Expose only enabled server tools for the selected product environment, preserving asset, folder, transformation, derived-resource, metadata, configuration, analysis, and flow identifiers.
Write scope: Upload, transform, rename, delete, organize, tag, configure presets/mappings/webhooks, manage metadata definitions, run analyses, and create/manage MediaFlows automations.
Authentication: Hosted servers use browser OAuth by default and prompt for a product environment; most accept Cloudinary URL or individual API credential headers. Local servers require manual credentials.
Approval boundary: Confirm product environment, server, target asset or configuration, current value, proposed change, derived-output impact, and workflow state before destructive or production-affecting operations.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access3
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Cloudinary ships them.
Single-platform patterns
- Media transformation and campaign-asset console
- Media production console
- Localization and variant studio
- Review-and-approval queue
Multi-platform compositions
- Cloudinary + publishing or campaign platform: media production console
- Cloudinary + DAM or CMS + social or video distribution system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
MCP / agent-role validationRepresentative source
https://cloudinary.com/documentation/cloudinary_llm_mcp ↗Cloudinary documents five distinct first-party servers for asset management, environment configuration, structured metadata, analysis, and MediaFlows.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
Developer docsSource inventory
https://cloudinary.com/documentation ↗First-party API and product documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://cloudinary.com/ ↗Product overview.
- Publisher updated
- Jul 6, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
NotificationsSource inventory
https://cloudinary.com/documentation/notifications ↗First-party webhook and callback guidance.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.