Cloudinary MCP Servers
by
Provides a suite of Model Context Protocol servers that enable AI‑driven upload, transformation, analysis, and workflow automation of media assets on Cloudinary.
Cloudinary MCP Servers Overview
What is Cloudinary MCP Servers?
Cloudinary MCP Servers expose Cloudinary's full media management capabilities through standardized MCP endpoints, allowing conversational AI tools to interact with assets, configurations, metadata, analysis services, and low‑code workflow automation.
How to use Cloudinary MCP Servers?
- Choose remote or local deployment – remote servers are ready‑to‑use via URLs; local servers run on your machine with npm packages.
- Configure credentials – set
CLOUDINARY_URL(or individual env vars) with your Cloudinary cloud name, API key, and secret. - Start the server – for local servers run the provided
npxcommand; for remote servers simply point your client to the supplied URL. - Consume the MCP endpoint – send MCP‑formatted requests from LLM‑enabled applications (e.g., Claude, Cursor) to perform asset uploads, transformations, metadata queries, AI analysis, or workflow triggers.
Key features of Cloudinary MCP Servers
- Asset Management: upload, search, transform, organize, and download media assets.
- Environment Config: manage upload presets, transformation settings, streaming profiles, and webhooks.
- Structured Metadata: create, validate, and query custom metadata fields for richer asset taxonomy.
- Analysis: AI‑powered tagging, moderation, captioning, object detection, quality assessment, and more.
- MediaFlows: low‑code workflow creation and automation, including conditional logic based on asset properties.
- Remote & Local options: instantly use hosted endpoints or run fully customizable local instances.
Use cases of Cloudinary MCP Servers
- AI‑driven content creation: let LLMs generate images, then automatically upload and tag them.
- Automated moderation pipelines: analyze new uploads for prohibited content and trigger alerts.
- Dynamic asset catalogs: enrich media libraries with structured metadata searchable via natural language.
- Custom media workflows: automate transcoding, watermarking, and publishing steps using MediaFlows.
- Enterprise media asset management: provide conversational interfaces for non‑technical users to locate and manipulate assets.
FAQ
Q: Do I need to install anything to use the remote servers? A: No. Remote servers are hosted by Cloudinary; just configure the endpoint URL and authentication.
Q: Which command should I use for local servers?
A: The recommended approach is npx with the appropriate package, e.g., npx -y --package @cloudinary/asset-management -- mcp start.
Q: How are credentials supplied?
A: You can set CLOUDINARY_URL (preferred) or individual env vars CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET.
Q: Can I run multiple MCP servers simultaneously? A: Yes. Each server runs on its own port; configure them independently in your client.
Q: Are there any paid features? A: Advanced AI analysis, high‑volume usage, custom metadata, and premium transformations may require a paid Cloudinary plan.
Cloudinary MCP Servers's README
Cloudinary MCP Servers
Model Context Protocol (MCP) is a new, standardized protocol for managing context between large language models (LLMs) and external systems. This repository provides comprehensive MCP servers for Cloudinary's media management platform, enabling you to use natural language to upload, transform, analyze, and organize your media assets directly from AI applications like Cursor and Claude.
With these MCP servers, you can seamlessly manage your entire media workflow through conversational AI - from uploading and transforming images and videos, to configuring automated processing pipelines, analyzing content with AI-powered tools, and organizing assets with structured metadata. Whether you're building media-rich applications, managing large asset libraries, or automating content workflows, these servers provide direct access to Cloudinary's full suite of media optimization and management capabilities.
The following MCP servers are available for Cloudinary:
| Server Name | Description | GitHub Repository | Remote MCP Server |
|---|---|---|---|
| Asset Management | Upload, manage, and transform your media assets with advanced search and organization capabilities | @cloudinary/asset-management | asset-management SSE |
| Environment Config | Configure and manage your Cloudinary environment settings, upload presets, and transformations | @cloudinary/environment-config | environment-config SSE |
| Structured Metadata | Create, manage, and query structured metadata fields for enhanced asset organization and searchability | @cloudinary/structured-metadata | structured-metadata SSE |
| Analysis | Leverage AI-powered content analysis, moderation, and auto-tagging capabilities for your media assets | @cloudinary/analysis | analysis SSE |
| MediaFlows | Build and manage low-code workflow automations for images and videos with AI-powered assistance | MediaFlows MCP | mediaflows MCP |
Table of Contents
- Documentation
- Installation
- Configuration Examples
- Authentication
- Features by Server
- Need access to more Cloudinary tools?
- Troubleshooting
- Paid Features
- License
Documentation
For detailed guides, tutorials, and comprehensive documentation on using Cloudinary's MCP servers:
- Cloudinary MCP and LLM Tool Documentation - Complete guide to integrating Cloudinary with AI/LLM applications
- MediaFlows MCP Documentation - Setup instructions and guidelines for using the MediaFlows (MCP) server
Installation
Remote MCP Servers (Recommended)
Remote MCP servers are hosted by Cloudinary and ready to use immediately. No local installation required.
Local MCP Servers
Local MCP servers run on your machine using npm packages. Choose this option if you need more control or customization.
Note: You'll need to configure your environment variables (CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET) with your actual credentials after installation.
Configuration Examples
Remote MCP Servers Configuration
Remote servers are hosted by Cloudinary and accessed via URL:
{
"mcpServers": {
"cloudinary-asset-mgmt-remote": {
"url": "https://asset-management.mcp.cloudinary.com/sse"
},
"cloudinary-env-config-remote": {
"url": "https://environment-config.mcp.cloudinary.com/sse"
},
"cloudinary-smd-remote": {
"url": "https://structured-metadata.mcp.cloudinary.com/sse"
},
"cloudinary-analysis-remote": {
"url": "https://analysis.mcp.cloudinary.com/sse"
},
"mediaflows": {
"url": "https://mediaflows.mcp.cloudinary.com/v2/mcp"
}
}
}
Local MCP Servers Configuration
Local servers run on your machine using npm packages:
Option 1: Using CLOUDINARY_URL environment variable (Recommended)
{
"mcpServers": {
"cloudinary-asset-mgmt": {
"command": "npx",
"args": ["-y", "--package", "@cloudinary/asset-management", "--", "mcp", "start"],
"env": {
"CLOUDINARY_URL": "cloudinary://api_key:api_secret@cloud_name"
}
},
"cloudinary-env-config": {
"command": "npx",
"args": ["-y", "--package", "@cloudinary/environment-config", "--", "mcp", "start"],
"env": {
"CLOUDINARY_URL": "cloudinary://api_key:api_secret@cloud_name"
}
},
"cloudinary-smd": {
"command": "npx",
"args": ["-y", "--package", "@cloudinary/structured-metadata", "--", "mcp", "start"],
"env": {
"CLOUDINARY_URL": "cloudinary://api_key:api_secret@cloud_name"
}
},
"cloudinary-analysis": {
"command": "npx",
"args": ["-y", "--package", "@cloudinary/analysis", "--", "mcp", "start"],
"env": {
"CLOUDINARY_URL": "cloudinary://api_key:api_secret@cloud_name"
}
}
}
}
Option 2: Using individual environment variables
{
"mcpServers": {
"cloudinary-asset-mgmt": {
"command": "npx",
"args": ["-y", "--package", "@cloudinary/asset-management", "--", "mcp", "start"],
"env": {
"CLOUDINARY_CLOUD_NAME": "cloud_name",
"CLOUDINARY_API_KEY": "api_key",
"CLOUDINARY_API_SECRET": "api_secret"
}
}
}
}
Option 3: Using command line arguments
{
"mcpServers": {
"cloudinary-asset-mgmt": {
"command": "npx",
"args": [
"-y", "--package", "@cloudinary/asset-management",
"--",
"mcp", "start",
"--cloud-name", "cloud_name",
"--api-key", "api_key",
"--api-secret", "api_secret"
]
}
}
}
MediaFlows MCP Server Configuration
For MediaFlows, use the following configuration:
{
"mcpServers": {
"mediaflows": {
"url": "https://mediaflows.mcp.cloudinary.com/v2/mcp",
"headers": {
"cld-cloud-name": "cloud_name",
"cld-api-key": "api_key",
"cld-secret": "api_secret"
}
}
}
}
Authentication
When running MCP servers locally, authentication can be configured in several ways:
Option 1: Individual environment variables (Recommended)
export CLOUDINARY_CLOUD_NAME="cloud_name"
export CLOUDINARY_API_KEY="api_key"
export CLOUDINARY_API_SECRET="api_secret"
Option 2: CLOUDINARY_URL environment variable
export CLOUDINARY_URL="cloudinary://api_key:api_secret@cloud_name"
Option 3: Command line arguments
Pass credentials directly as arguments (see configuration examples above)
You can find your Cloudinary credentials in your Cloudinary Console Dashboard under Settings > Security.
Features by Server
Asset Management Server
- Upload and manage media assets (images, videos, raw files)
- Search and organize assets with advanced filtering capabilities
- Handle asset operations and transformations
- Manage folders, tags, and asset relationships
- Generate archives and download links
Environment Config Server
- Configure upload presets and transformation settings
- Manage streaming profiles and webhook notifications
- Set up upload mappings
Structured Metadata Server
- Create and manage structured metadata fields
- Configure conditional metadata rules and validation
- Organize and search metadata configurations
- Handle metadata field relationships and ordering
Analysis Server
- AI-powered content analysis including tagging, moderation, and captioning
- Object detection and recognition with multiple AI models
- Image quality analysis and watermark detection
- Content moderation and safety analysis
- Fashion, text, and anatomy detection capabilities
MediaFlows Server
- Build and manage workflow automations using natural language
- Query existing PowerFlow automations in your environment
- Create conditional logic based on metadata, tags, and asset properties
- Automate asset moderation, approval, and notification workflows
- Debug and understand existing automation configurations
Need access to more Cloudinary tools?
We're continuing to add more functionality to these MCP servers. If you'd like to leave feedback, file a bug or provide a feature request, please open an issue on this repository.
Troubleshooting
"Claude's response was interrupted..."
If you see this message, Claude likely hit its context-length limit and stopped mid-reply. This happens most often on servers that trigger many chained tool calls such as the asset management server with large asset listings.
To reduce the chance of running into this issue:
- Try to be specific, keep your queries concise.
- If a single request calls multiple tools, try to break it into several smaller tool calls to keep the responses short.
- Use filtering parameters to limit the scope of asset searches and listings.
Authentication Issues
Ensure your Cloudinary credentials are correctly configured and have the necessary permissions for the operations you're trying to perform.
Paid Features
Some features may require a paid Cloudinary plan. Ensure your Cloudinary account has the necessary subscription level for the features you intend to use, such as:
- Advanced AI analysis features
- High-volume API usage
- Custom metadata fields
- Advanced transformation capabilities
License
Licensed under the MIT License. See LICENSE file for details.
Cloudinary MCP Servers Reviews
Login Required
Please log in to share your review and rating for this MCP.
Actions
Cloudinary MCP Servers's Information
- Author
- cloudinary
- Category
- Cloud Platforms
- License
- MIT License
- Stars
- 4
- Updated
- 8 days ago
Configuration
{
"mcpServers": {
"cloudinary-asset-mgmt": {
"command": "npx",
"args": [
"-y",
"--package",
"@cloudinary/asset-management",
"--",
"mcp",
"start"
],
"env": {
"CLOUDINARY_URL": "cloudinary://<API_KEY>:<API_SECRET>@<CLOUD_NAME>"
}
},
"cloudinary-env-config": {
"command": "npx",
"args": [
"-y",
"--package",
"@cloudinary/environment-config",
"--",
"mcp",
"start"
],
"env": {
"CLOUDINARY_URL": "cloudinary://<API_KEY>:<API_SECRET>@<CLOUD_NAME>"
}
},
"cloudinary-structured-metadata": {
"command": "npx",
"args": [
"-y",
"--package",
"@cloudinary/structured-metadata",
"--",
"mcp",
"start"
],
"env": {
"CLOUDINARY_URL": "cloudinary://<API_KEY>:<API_SECRET>@<CLOUD_NAME>"
}
},
"cloudinary-analysis": {
"command": "npx",
"args": [
"-y",
"--package",
"@cloudinary/analysis",
"--",
"mcp",
"start"
],
"env": {
"CLOUDINARY_URL": "cloudinary://<API_KEY>:<API_SECRET>@<CLOUD_NAME>"
}
}
}
}Configure Clients
Similar MCP Servers like Cloudinary MCP Servers
Explore related MCPs that share similar capabilities and solve comparable challenges
Aws Mcp Servers
Officialby awslabs
Provides specialized servers that expose AWS capabilities through the Model Context Protocol, enabling AI assistants to retrieve up-to-date documentation, execute API calls, and automate infrastructure workflows directly within development environments.
Cloudflare MCP Server
by cloudflare
Provides a collection of Model Context Protocol servers that enable MCP‑compatible clients to interact with Cloudflare services such as Workers, Observability, Radar, and more, allowing natural‑language driven management of configurations, data, and operations.
MCP Server Kubernetes
by Flux159
Connects to a Kubernetes cluster and offers a unified MCP interface for kubectl, Helm, port‑forwarding, diagnostics, and non‑destructive read‑only mode.
EdgeOne Pages MCP
by TencentEdgeOne
Deploy HTML, folders, or zip archives to EdgeOne Pages and instantly obtain a public URL for fast edge delivery.
AWS MCP Server
by rishikavikondala
Provides Model Context Protocol tools for performing AWS S3 and DynamoDB operations, with automatic logging and audit access via the `audit://aws-operations` endpoint.
Mcp Confluent
by confluentinc
Enables AI assistants to manage Confluent Cloud resources such as Kafka topics, connectors, and Flink SQL statements through natural‑language interactions.
Alibaba Cloud Ops MCP Server
Officialby aliyun
Enables AI assistants to operate Alibaba Cloud resources such as ECS, Cloud Monitor, OOS and other services through seamless integration with Alibaba Cloud APIs via the Model Context Protocol.
Sample MCP Server S3
by aws-samples
Retrieve PDF documents and other S3 objects through Model Context Protocol resources, enabling LLMs to pull data directly from AWS S3 buckets.
Mcp Nomad Go
by kocierik
Connects to HashiCorp Nomad and exposes Model Context Protocol endpoints for job, deployment, node, allocation, variable, volume, ACL, Sentinel, and cluster management via a Go‑based server.