Cloudinary MCP Server
About
Model Context Protocol (MCP) Server for Cloudinary API
Details
- Author
- yoavniran
- Downloads
- 242
- Categories
- Other
Jump to
- Upload assets to Cloudinary via URL, file, or base64
- Delete assets by public ID or asset ID
- Retrieve detailed asset information including metadata
- Search assets with query expressions and pagination
- View Cloudinary usage report (storage, credits, bandwidth, etc.)
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Cloudinary MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install and configure by adding an entry to your MCP client’s configuration (e.g., claude_desktop_config.json) with the command npx -y cloudinary-mcp-server and environment variables CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY, and CLOUDINARY_API_SECRET. The server provides five tools: upload, delete-asset, get-asset, find-assets, and get-usage.
upload
Upload a file (asset) to Cloudinary
delete-asset
Delete a file (asset) from Cloudinary
get-asset
Get the details of a specific file (asset)
find-assets
Search for existing files (assets) in Cloudinary with a query expression
get-usage
Get a report on the status of your product environment usage, including storage, credits, bandwidth, requests, number of resources, and add-on usage
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"cloudinary mcp server": {
"cloudinary-mcp-server": {
"command": "npx",
"args": [
"-y",
"cloudinary-mcp-server"
],
"env": {
"CLOUDINARY_CLOUD_NAME": "<cloud name>",
"CLOUDINARY_API_KEY": "<api-key>",
"CLOUDINARY_API_SECRET": "<api-secret>"
}
}
}
}
}
McpServers
{
"cloudinary-mcp-server": {
"command": "npx",
"args": [
"-y",
"cloudinary-mcp-server"
],
"env": {
"CLOUDINARY_CLOUD_NAME": "<cloud name>",
"CLOUDINARY_API_KEY": "<api-key>",
"CLOUDINARY_API_SECRET": "<api-secret>"
}
}
}
Cloudinary MCP Server
<a href="https://glama.ai/mcp/servers/@yoavniran/cloudinary-mcp-server">
</a>
<p align="center">
<a href="https://badge.fury.io/js/cloudinary-mcp-server">
</a>
</p>
A Model Context Protocol server that exposes Cloudinary Upload & Admin API methods as tools by AI assistants.
This integration allows AI systems to trigger and interact with your Cloudinary cloud.
How It Works
The MCP server:
- Makes calls on your behalf to the Cloudinary API
- Enables uploading of assets to Cloudinary
- Enables management of assets in your Cloudinary cloud
It relies on the Cloudinary API to perform these actions. Not all methods and parameters are supported.
More will be added over time.
Open an issue with a request for specific method if you need it.
Benefits
- Turn your Cloudinary cloud actions into callable tools for AI assistants
- Turn your Cloudinary assets into data for AI assistants
Usage with Claude Desktop
Prerequisites
- NodeJS
- MCP Client (like Claude Desktop App)
- Create & Copy Cloudinary API Key/Secret at: API KEYS
Installation
To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json:
{
"mcpServers": {
"cloudinary-mcp-server": {
"command": "npx",
"args": ["-y", "cloudinary-mcp-server"],
"env": {
"CLOUDINARY_CLOUD_NAME": "<cloud name>",
"CLOUDINARY_API_KEY": "<api-key>",
"CLOUDINARY_API_SECRET": "<api-secret>"
}
}
}
}
- CLOUDINARY_CLOUD_NAME - your cloud name
- CLOUDINARY_API_KEY - The API Key for your cloud
- CLOUDINARY_API_SECRET - The API Secret for your cloud
Tools
The following tools are available:
1. upload
- Description: Upload a file (asset) to Cloudinary
- Parameters:
- source: URL, file path, base64 content, or binary data to upload
- folder: Optional folder path in Cloudinary
- publicId: Optional public ID for the uploaded asset
- resourceType: Type of resource to upload (image, video, raw, auto)
- tags: Comma-separated list of tags to assign to the asset
2. delete-asset
- Description: Delete a file (asset) from Cloudinary
- Parameters:
- publicId: The public ID of the asset to delete
- assetId: The asset ID of the asset to delete
3. get-asset
- Description: Get the details of a specific file (asset)
- Parameters:
- assetId: The Cloudinary asset ID
- publicId: The public ID of the asset
- resourceType: Type of asset (image, raw, video)
- type: Delivery type (upload, private, authenticated, etc.)
- tags: Whether to include the list of tag names
- context: Whether to include contextual metadata
- metadata: Whether to include structured metadata
4. find-assets
- Description: Search for existing files (assets) in Cloudinary with a query expression
- Parameters:
- expression: Search expression (e.g. 'tags=cat' or 'public_id:folder/*')
- resourceType: Resource type (image, video, raw)
- maxResults: Maximum number of results (1-500)
- nextCursor: Next cursor for pagination
- tags: Include tags in the response
- context: Include context in the response
5. get-usage
- Description: Get a report on the status of your product environment usage, including storage, credits, bandwidth, requests, number of resources, and add-on usage
- Parameters:
- date: Optional. The date for the usage report in the format: yyyy-mm-dd. Must be within the last 3 months. Default: the current date
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



