cloudinary-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDINARY_API_KEY | Yes | The API Key for your Cloudinary cloud | |
| CLOUDINARY_API_SECRET | Yes | The API Secret for your Cloudinary cloud | |
| CLOUDINARY_CLOUD_NAME | Yes | Your Cloudinary cloud name |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uploadC | Upload a file (asset) to Cloudinary |
| delete-assetB | Delete a file (asset) from Cloudinary |
| get-assetC | Get the details of a specific file (asset) |
| find-assetsC | Search for existing files (assets) in Cloudinary with a query expression |
| get-usageC | Get a report on the status of your product environment usage, including storage, credits, bandwidth, requests, number of resources, and add-on usage |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: delete, search, get details, get usage report, and upload. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
Four tools follow a consistent verb-noun pattern (delete-asset, find-assets, get-asset, get-usage), but 'upload' deviates by omitting the noun. This minor inconsistency slightly reduces predictability, though the naming remains readable and mostly uniform.
With 5 tools, this server is well-scoped for managing Cloudinary assets. Each tool earns its place by covering essential operations (upload, get, search, delete, usage reporting), avoiding bloat while providing complete core functionality.
The toolset covers core CRUD operations for assets (upload, get, delete, search) and includes usage reporting, offering good coverage for the Cloudinary domain. A minor gap is the lack of update or transformation tools for assets, but agents can work around this by re-uploading or using other methods.