Can AI agents automate Cloudinary?

Cloudinary is automatable today through its REST Admin and Upload APIs at https://api.cloudinary.com/v1_1 and through first-party MCP servers. This record is Cloudinary's media platform: upload, search, transformations, metadata, analysis, and MediaFlows. It is not Adobe Experience Manager or Bynder. The Admin API is rate-limited REST with HTTP Basic authentication using API key and secret. The Upload API is not rate-limited and accepts Basic Auth or a SHA signature with timestamp. Self-service OAuth 2.0 for Cloudinary APIs is documented as Beta, with authorization-code tokens and five-minute access tokens. Official backend SDKs wrap these REST APIs. The official CLI (cld, package cloudinary-cli) wraps Admin and Upload methods, supports browser OAuth login or a CLOUDINARY_URL, and returns structured output. Webhook notifications POST JSON to configured URLs after API or Console actions. Cloudinary hosts five first-party MCP servers in this identity: Asset Management at https://asset-management.mcp.cloudinary.com/mcp, Environment Config, Structured Metadata, Analysis at https://analysis.mcp.cloudinary.com/sse, and MediaFlows at https://mediaflows.mcp.cloudinary.com/v2/mcp. Remote Asset Management, Environment Config, and Structured Metadata default to OAuth and also accept API-key headers. Remote Analysis is OAuth-only. MediaFlows MCP authenticates with API-key headers, supports PowerFlows only, creates flows inactive, and does not modify existing automations. Paid add-on tiers sit behind paid Cloudinary plans. iPaaS connector catalogs were not opened. Computer-use viability is unassessed. API and MCP both score 8. API is the best path because it is the single documented production surface with webhooks and official SDKs, while MCP is split across five servers with Analysis and MediaFlows constraints.

Best path today: api · Overall automatability: 8/10