Cloudinary Asset Management MCP Server

Summary

Table of Contents

• Cloudinary Asset Management MCP Server
  • Installation
  • Configuration
  • Authentication
  • Available Tools
  • Custom Tools
• Development
  • Building from Source
  • Contributions

Installation

MCP Bundle (Desktop Extension)

Install the MCP server as a Desktop Extension using the pre-built mcp-server.mcpb file:

Simply drag and drop the mcp-server.mcpb file onto Claude Desktop to install the extension.

The MCP bundle package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.

[!NOTE] MCP bundles provide a streamlined way to package and distribute MCP servers. Learn more about Desktop Extensions.

Cursor

Or manually:

1. Open Cursor Settings
2. Select Tools and Integrations
3. Select New MCP Server
4. If the configuration file is empty paste the following JSON into the MCP Server Configuration:

{
  "mcpServers": {
    "CloudinaryAssetMgmt": {
      "command": "npx",
      "args": [
        "@cloudinary/asset-management-mcp",
        "start",
        "--server-index",
        "...",
        "--region",
        "...",
        "--api-host",
        "...",
        "--api-key",
        "...",
        "--api-secret",
        "...",
        "--oauth2",
        "...",
        "--cloud-name",
        "..."
      ]
    }
  }
}

Claude Code CLI

claude mcp add @cloudinary/asset-management-mcp npx @cloudinary/asset-management-mcp start -- --server-index ... --region ... --api-host ... --api-key ... --api-secret ... --oauth2 ... --cloud-name ...

Windsurf

Refer to Official Windsurf documentation for latest information

1. Open Windsurf Settings
2. Select Cascade on left side menu
3. Click on Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)
4. Click on View raw config to open up the mcp configuration file.
5. If the configuration file is empty paste the full json

{
  "mcpServers": {
    "CloudinaryAssetMgmt": {
      "command": "npx",
      "args": [
        "@cloudinary/asset-management-mcp",
        "start",
        "--server-index",
        "...",
        "--region",
        "...",
        "--api-host",
        "...",
        "--api-key",
        "...",
        "--api-secret",
        "...",
        "--oauth2",
        "...",
        "--cloud-name",
        "..."
      ]
    }
  }
}

VS Code

Refer to Official VS Code documentation for latest information

1. Open Command Palette
2. Search and open MCP: Open User Configuration. This should open mcp.json file
3. If the configuration file is empty paste the full json

{
  "mcpServers": {
    "CloudinaryAssetMgmt": {
      "command": "npx",
      "args": [
        "@cloudinary/asset-management-mcp",
        "start",
        "--server-index",
        "...",
        "--region",
        "...",
        "--api-host",
        "...",
        "--api-key",
        "...",
        "--api-secret",
        "...",
        "--oauth2",
        "...",
        "--cloud-name",
        "..."
      ]
    }
  }
}

Claude Desktop

Claude Desktop doesn't yet support SSE/remote MCP servers.

You need to do the following

1. Open claude Desktop
2. Open left hand side pane, then click on your Username
3. Go to Settings
4. Go to Developer tab (on the left hand side)
5. Click on Edit Config Paste the following config in the configuration

{
  "mcpServers": {
    "CloudinaryAssetMgmt": {
      "command": "npx",
      "args": [
        "@cloudinary/asset-management-mcp",
        "start",
        "--server-index",
        "...",
        "--region",
        "...",
        "--api-host",
        "...",
        "--api-key",
        "...",
        "--api-secret",
        "...",
        "--oauth2",
        "...",
        "--cloud-name",
        "..."
      ]
    }
  }
}

Stdio installation via npm

To start the MCP server, run:

npx @cloudinary/asset-management-mcp start --server-index ... --region ... --api-host ... --api-key ... --api-secret ... --oauth2 ... --cloud-name ...

For a full list of server arguments, run:

npx @cloudinary/asset-management-mcp --help

Configuration

Environment Variables

The MCP server supports the following environment variables:

Variable	Description	Required
CLOUDINARY_CLOUD_NAME	Your Cloudinary cloud name	Yes
CLOUDINARY_API_KEY	Your Cloudinary API key	Yes
CLOUDINARY_API_SECRET	Your Cloudinary API secret	Yes
CLOUDINARY_URL	Complete Cloudinary URL (alternative to individual vars)	No

CLOUDINARY_URL Format

You can use a single CLOUDINARY_URL instead of individual variables:

CLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME

Authentication

The MCP server uses your Cloudinary API key and secret for authentication:

{
  "env": {
    "CLOUDINARY_CLOUD_NAME": "demo",
    "CLOUDINARY_API_KEY": "123456789012345",
    "CLOUDINARY_API_SECRET": "abcdefghijklmnopqrstuvwxyz12"
  }
}

Available Tools

The MCP server exposes Cloudinary's Asset Management API as tools. Use your AI application to discover and invoke the available tools for uploading, managing, searching, and transforming your media assets.

Custom Tools

This MCP server includes two powerful custom tools:

get-tx-reference

Retrieves the complete Cloudinary transformation reference documentation.

When to use:

• Before creating or modifying transformations
• When user asks about image/video effects, resizing, cropping, filters

Example:

Use get-tx-reference to learn about available transformations

transform-asset

Applies transformations to existing assets using Cloudinary's explicit API.

Parameters:

• publicId - The asset's public ID
• transformations - Transformation string (e.g., c_fill,w_300,h_200)
• resourceType - Type: image, video, or raw (default: image)
• invalidate - Invalidate CDN cache (default: false)

Example:

Transform asset "sample" with transformations "c_fill,w_500,h_500/e_sepia"

Development

Building from Source

Prerequisites

• Node.js v20 or higher
• npm, pnpm, bun, or yarn

Build Steps

# Clone the repository
git clone https://github.com/cloudinary/asset-management-mcp.git
cd asset-management-mcp

# Install dependencies
npm install

# Build the project
npm run build

# Run locally
npm start

Project Structure

asset-management-mcp/
├── src/
│   ├── hooks/              # Custom authentication hooks
│   ├── mcp-server/         # MCP server implementation
│   │   ├── server.ts       # Main server (auto-generated)
│   │   ├── server.extensions.ts  # Custom tools (manual)
│   │   └── tools/          # Generated tool wrappers
│   ├── funcs/              # API function implementations
│   └── models/             # Type definitions
├── .github/
│   └── workflows/          # CI/CD workflows
└── .speakeasy/             # Speakeasy configuration

Contributions

While we value contributions to this MCP Server, the code is generated programmatically. Any manual changes to generated files will be overwritten on the next generation.

What you can contribute:

• ✅ Custom tools in server.extensions.ts
• ✅ Custom hooks in src/hooks/
• ✅ Documentation improvements
• ✅ Bug reports and feature requests

Generated files (do not edit):

• ❌ src/mcp-server/server.ts
• ❌ src/mcp-server/tools/*.ts
• ❌ src/funcs/*.ts
• ❌ src/models/*.ts

We look forward to hearing your feedback. Feel free to open a PR or issue with a proof of concept and we'll do our best to include it in a future release.

---

MCP Server Created by Speakeasy