Cloudinary Integration
STDIOModel Context Protocol server exposing Cloudinary Upload & Admin API methods for AI assistants.
Model Context Protocol server exposing Cloudinary Upload & Admin API methods for AI assistants.
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.
The MCP server:
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.
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 nameCLOUDINARY_API_KEY
- The API Key for your cloudCLOUDINARY_API_SECRET
- The API Secret for your cloudThe following tools are available:
upload
source
: URL, file path, base64 content, or binary data to uploadfolder
: Optional folder path in CloudinarypublicId
: Optional public ID for the uploaded assetresourceType
: Type of resource to upload (image, video, raw, auto)tags
: Comma-separated list of tags to assign to the assetdelete-asset
publicId
: The public ID of the asset to deleteassetId
: The asset ID of the asset to deleteget-asset
assetId
: The Cloudinary asset IDpublicId
: The public ID of the assetresourceType
: Type of asset (image, raw, video)type
: Delivery type (upload, private, authenticated, etc.)tags
: Whether to include the list of tag namescontext
: Whether to include contextual metadatametadata
: Whether to include structured metadatafind-assets
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 paginationtags
: Include tags in the responsecontext
: Include context in the responseget-usage
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