Cloudinary MCP Server
Servidor MCP de Cloudinary
Este servidor MCP proporciona herramientas para cargar imágenes y videos a Cloudinary a través de Claude Desktop y clientes MCP compatibles.
Instalación
Requisitos: Node.js
Instale Node.js (versión 18 o superior) y npm desde nodejs.org
Verificar la instalación:
node --version npm --version
Instalar usando npx (recomendado)
Navegue hasta el directorio de configuración de Claude:
Windows:
C:\Users\NAME\AppData\Roaming\ClaudemacOS:
~/Library/Application Support/Claude/
También puede encontrar estos directorios dentro de la aplicación Claude Desktop: Claude Desktop > Configuración > Desarrollador > Editar configuración
Agregue la siguiente configuración a su archivo de configuración de MCP:
{
"mcpServers": {
"cloudinary": {
"command": "npx",
"args": ["@felores/cloudinary-mcp-server@latest"],
"env": {
"CLOUDINARY_CLOUD_NAME": "your_cloud_name",
"CLOUDINARY_API_KEY": "your_api_key",
"CLOUDINARY_API_SECRET": "your_api_secret"
}
}
}
}Asegúrese de reemplazar las variables de entorno con sus credenciales de Cloudinary desde la consola de Cloudinary .
Instalación para desarrolladores
Si desea modificar el servidor o contribuir al desarrollo:
Clonar el repositorio:
git clone https://github.com/felores/cloudinary-mcp-server.git
cd cloudinary-mcp-serverInstalar dependencias y compilar:
npm install
npm run buildRelated MCP server: Image Analysis MCP Server
Instrucciones de configuración
Primero, asegúrese de tener una cuenta de Cloudinary y obtenga sus credenciales de la consola de Cloudinary :
Nombre de la nube
Clave API
Secreto de API
Agregue la configuración del servidor a su archivo de configuración MCP de Claude/Cline:
{
"mcpServers": {
"cloudinary": {
"command": "node",
"args": ["c:/path/to/cloudinary-mcp-server/dist/index.js"],
"env": {
"CLOUDINARY_CLOUD_NAME": "your_cloud_name",
"CLOUDINARY_API_KEY": "your_api_key",
"CLOUDINARY_API_SECRET": "your_api_secret"
}
}
}
}Para la aplicación de escritorio Claude, edite el archivo de configuración en la ubicación adecuada para su sistema operativo.
Instalar dependencias y construir el servidor:
npm install
npm run buildHerramientas disponibles
subir
Sube imágenes y vídeos a Cloudinary.
Parámetros:
file(obligatorio): Ruta al archivo, URL o URI de datos base64 para cargarresource_type(opcional): Tipo de recurso ('imagen', 'video' o 'raw')public_id(opcional): ID público personalizado para el activo cargadooverwrite(opcional): si desea sobrescribir los activos existentes con la misma identificación públicatags(opcional): Matriz de etiquetas para asignar al activo cargado
Ejemplo de uso en Claude/Cline:
use_mcp_tool({
server_name: "cloudinary",
tool_name: "upload",
arguments: {
file: "path/to/image.jpg",
resource_type: "image",
public_id: "my-custom-id"
}
});Available Tools
1 tooluploadB
Upload media (images/videos) to Cloudinary. For large files, the upload is processed in chunks and returns a streaming response. The uploaded asset will be available at:
HTTP: http://res.cloudinary.com/{cloud_name}/{resource_type}/upload/v1/{public_id}.{format}
HTTPS: https://res.cloudinary.com/{cloud_name}/{resource_type}/upload/v1/{public_id}.{format} where {cloud_name} is your Cloudinary cloud name, resource_type is 'image' or 'video', and format is determined by the file extension.
Inputs: file (required), resource_type, public_id, overwrite, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility for ambiguity or overlap between tools. The 'upload' tool has a clear, singular purpose of uploading media to Cloudinary, making it impossible for an agent to misselect among multiple options.
Since there is only one tool named 'upload', it inherently follows a consistent naming pattern. There are no other tools to compare against, so no inconsistencies can arise in verb style, case conventions, or other naming aspects.
A single tool is too few for a Cloudinary server, which typically handles a wide range of media operations like upload, delete, transform, list, and fetch. This minimal set severely limits functionality and will likely cause agent failures due to missing essential operations for the domain.
The tool set is severely incomplete for a Cloudinary media management server. It only provides upload functionality, with glaring gaps such as no delete, update, list, search, or transformation tools. This makes it impossible for agents to perform basic CRUD or lifecycle operations in the domain.
Maintenance
Related MCP Connectors
Upload, generate, organize, search, and transform images, videos, and files with AI-powered tools.
Upload, generate, organize, search, and transform images, videos, and files with AI-powered tools.
MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.
Manage Cloudinary upload presets, named transformations, mappings, triggers, and streaming profiles.
Related MCP Servers
- AlicenseAqualityDmaintenanceThis server generates placeholder image URLs from various providers, supporting input validation and integration with desktop applications like Claude and Cursor.112MIT
- AlicenseCqualityDmaintenanceA server that accepts image URLs and analyzes their content using GPT-4-turbo, enabling Claude AI assistants to understand and describe images through natural language.28MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server for image processing and cloud uploads that automates resizing, converting, optimizing, and uploading images to services like AWS S3, Cloudflare R2, and Google Cloud Storage.25 npm18MIT
- AlicenseAqualityDmaintenanceMCP server for uploading images to ImgBB from Claude-compatible clients.3MIT