Spark
Sign In
MCP Connector

Upload Media to Cloudinary

MCP server for uploading images and videos to Cloudinary from Claude Desktop - files, URLs, or base64, with custom public IDs and tags.

Get from source
Works with cloudinary
Felo Restrepo
Own this? Claim it
91
Spark score
out of 100
Updated Mar 2025
Fresher alternatives ↓
Source checked Sep 10, 2026
Version 1.0.0
Models
universal
Add to Favorites

Why it matters

Integrate Cloudinary's media management capabilities into your Claude Desktop environment. This asset allows for seamless uploading of images and videos directly from your desktop client.

Outcomes

What it gets done

01

Upload images and videos to Cloudinary via file path, URL, or base64.

02

Configure Cloudinary credentials securely using environment variables.

03

Assign custom public IDs, tags, and specify resource types for uploaded media.

04

Overwrite existing resources with new uploads.

Source

Get it from source

Spark does not host a copy of it.

Open source

Reports

Agent outcome reports

No reports yet

Capabilities

Tools your agent gets

upload

Uploads images and videos to Cloudinary with support for file paths, URLs, or base64 data URIs

Overview

Cloudinary MCP Server

An MCP server that uploads images and videos to Cloudinary from Claude Desktop and compatible clients, accepting a local file path, URL, or base64 data URI, with control over resource type, public ID, tags, and overwrite behavior. Use it when Claude needs to push media, such as images, videos, or raw files, to a Cloudinary account directly, with a custom public ID or tags, instead of uploading manually through the Cloudinary console.

What it does

An MCP server that gives Claude Desktop and compatible MCP clients a single upload tool for Cloudinary, the media management platform. A file can be supplied as a local path, a URL, or a base64 data URI, and the server handles pushing it to the configured Cloudinary account as an image, video, or raw resource.

When to use - and when NOT to

Use it when a workflow in Claude needs to actually push media to Cloudinary - uploading a generated or local image or video, assigning it a predictable public ID for later reference, or tagging assets as they're uploaded. It requires a Cloudinary account and its three credentials, cloud name, API key, and API secret, configured as environment variables; without them the server cannot authenticate. It is upload-only based on the documented tool - there is no indication of tools for transforming, deleting, or listing existing Cloudinary assets, so tasks beyond pushing new media likely need the Cloudinary console or API directly.

Capabilities

The upload tool takes a required file, a path, URL, or base64 data URI, and optional resource_type (image, video, or raw), public_id, a custom identifier instead of an auto-generated one, overwrite, whether to replace an existing asset sharing that public ID, and tags, an array of labels to assign to the uploaded asset.

How to install

Requires Node.js 18+ and a Cloudinary account with credentials from the Cloudinary Console.

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

Add this to the Claude Desktop configuration file, replacing the credential placeholders with real values from the Cloudinary Console. For local development, clone the repository, then run npm install and npm run build.

Who it's for

Developers and content workflows that need Claude to upload images or videos to Cloudinary directly, with a predictable public ID and tags, instead of a manual upload step.

Source README

Cloudinary MCP Server

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

Cloudinary Server MCP server

Installation

Requirements: Node.js

  1. Install Node.js (version 18 or higher) and npm from nodejs.org
  2. Verify installation:
    node --version
npm --version

Install using npx (Recommended)

  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

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"
  }
});

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.