LabscoMCP early access ↗
feloresMCP SERVER

Cloudinary MCP Server

Uploads an image or video to Cloudinary from a path, a URL or base64, and hands back the delivery URL it now lives at.

by felores ↗Office Suites & Cloud File StorageCommunity

LABSCO SUMMARY

One tool, one job: get a file into Cloudinary and return the URL it now lives at.

Because the source can be a URL or base64 as well as a path, it slots straight after an image-generating step without anything touching your filesystem first. Set public_id yourself when the URL has to be predictable, and leave overwrite off if replacing an asset already at that ID would be a problem.

What it is

A single-purpose server over Cloudinary's upload API: one tool that takes media in and returns the hosted asset.

What you get

  • One upload tool that accepts a local file path, a URL, or a base64 data URI
  • resource_type to say whether it is an image, a video or a raw file
  • public_id to set the asset's identifier yourself, overwrite to decide whether an existing asset at that ID is replaced, and tags to label it at upload time
  • Large files are sent in chunks and return a streaming response
  • The asset comes back as its delivery URL — https://res.cloudinary.com/{cloud_name}/{resource_type}/upload/v1/{public_id}.{format}

Requirements

A Cloudinary account and three values from the Console's API Keys page: CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY and CLOUDINARY_API_SECRET. Node.js 18 or higher. Run it over stdio with npx @felores/cloudinary-mcp-server@latest.

Setup effort

One command plus a key — npx @felores/cloudinary-mcp-server@latest, then supply credentials

See installation options