Cloudinary Asset Management

io.github.subomiPublished by GitHub account subomiv0.8.11Updated Oct 24, 2026

Upload, organize, search, and transform images, videos, and files with AI-powered tools.

VerifiedSTDIODesktop onlyFiles & StorageMedia & Design

Overview

AI-generated overview

A local MCP server that lets an assistant upload, organize, search and transform images, videos and files in a Cloudinary account.

What you can do
Upload images, videos and other files to a Cloudinary account and organize them there, per the registry description of upload and organize tools. Search the stored media assets. Transform media through the AI-powered tools the description mentions. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth adding when an assistant should work with a Cloudinary media library: pushing new assets, tidying existing ones, finding media, or generating transformed versions of images and videos.
Requirements
Runs as a local process installed from the npm package sample-mcp, so Node.js is needed. Requires a Cloudinary account and three environment variables: CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY and CLOUDINARY_API_SECRET, all found in the Cloudinary dashboard. Desktop only.
Before you install
CLOUDINARY_API_KEY and CLOUDINARY_API_SECRET are secrets that grant access to the Cloudinary account; keep them out of shared configuration and logs. Uploading, organizing and transforming assets changes data in the account, and transformed or uploaded media is sent to Cloudinary's service.

Installation

In SourceWeft

  1. Open Cloudinary Asset Management in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.11LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.