Skip to main content
Glama
Cloudinary MCP Server

Cloudinary MCP Server

by felores

Cloudinary MCP Server

This MCP server provides tools for uploading images and videos to Cloudinary through Claude Desktop and compatible MCP clients.

Installation

Requirements: Node.js

  1. Install Node.js (version 18 or higher) and npm from nodejs.org

  2. Verify installation:

    node --version
    npm --version
  1. Navigate to the Claude configuration directory:

    • Windows: C:\Users\NAME\AppData\Roaming\Claude

    • macOS: ~/Library/Application Support/Claude/

    You can also find these directories inside the Claude Desktop app: Claude Desktop > Settings > Developer > Edit Config

  2. Add the following configuration to your MCP settings file:

{
  "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"
      }
    }
  }
}
  1. Make sure to replace the environment variables with your Cloudinary credentials from the Cloudinary Console.

Developer Installation

If you want to modify the server or contribute to development:

  1. Clone the repository:

git clone https://github.com/felores/cloudinary-mcp-server.git
cd cloudinary-mcp-server
  1. Install dependencies and build:

npm install
npm run build

Related MCP server: Image Analysis MCP Server

Setup Instructions

  1. First, ensure you have a Cloudinary account and get your credentials from the Cloudinary Console:

    • Cloud Name

    • API Key

    • API Secret

  2. Add the server configuration to your Claude/Cline MCP settings file:

{
  "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"
      }
    }
  }
}

For Claude desktop app, edit the configuration file at the appropriate location for your OS.

  1. Install dependencies and build the server:

npm install
npm run build

Available Tools

upload

Upload images and videos to Cloudinary.

Parameters:

  • file (required): Path to file, URL, or base64 data URI to upload

  • resource_type (optional): Type of resource ('image', 'video', or 'raw')

  • public_id (optional): Custom public ID for the uploaded asset

  • overwrite (optional): Whether to overwrite existing assets with the same public ID

  • tags (optional): Array of tags to assign to the uploaded asset

Example usage in 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 tool
uploadB

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:

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

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness1/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers