Get started free
All integrations

Cloudinary integration

Cloudinary media management API for uploading, transforming, and delivering images and videos. Upload files from URLs, local paths, or base64 data. Apply real-time transformations, manage assets with tags and folders, and deliver optimized media through CDN. Ideal for image optimization, video processing, and media-heavy applications.

39 toolsBasic authAPI docs

Common Cloudinary use cases

  • tag management
  • asset organization
  • folder navigation
  • tag cleanup
  • folder cleanup
  • preset management
  • preset modification
  • transformation cleanup
  • usage analysis
  • configuration review

What you can do with Cloudinary

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Asset, 10 operations

  • DELETEdelete_resources

    Deletes one or more assets from Cloudinary by their public IDs.

  • DELETEdelete_resources_by_prefix

    Deletes all assets matching a public_id prefix (folder path).

  • GETget_resources_by_asset_ids

    Retrieves assets by their unique asset IDs.

  • GETlist_resources

    Lists images, videos, or raw files in your Cloudinary account with optional filtering.

  • GETlist_resources_by_asset_folder

    Lists assets in a specific asset folder (dynamic folder mode only).

  • GETlist_resources_by_context

    Lists assets with specific contextual metadata.

  • GETlist_resources_by_tag

    Lists all assets that have a specific tag applied.

  • POSTrestore_resources

    Restores previously deleted assets from backup.

  • POSTsearch

    Searches for assets using powerful Lucene-like query expressions.

  • POSTvisual_search

    Finds images visually similar to a reference image.

Folder, 6 operations

  • POSTcreate_folder

    Creates a new folder in Cloudinary for organizing assets.

  • DELETEdelete_folder

    Deletes an empty folder from Cloudinary.

  • GETlist_folders

    Lists all root-level folders in your Cloudinary account.

  • GETlist_subfolders

    Lists all subfolders within a specified parent folder.

  • PUTrename_folder

    Renames or moves a Cloudinary folder to a new path.

  • GETsearch_folders

    Searches folders using a Lucene-like query expression.

Tag, 5 operations

  • POSTadd_tag

    Adds tags to one or more assets.

  • GETlist_tags

    Lists all tags used for organizing assets in your Cloudinary account.

  • POSTremove_all_tags

    Removes all tags from specified assets.

  • POSTremove_tag

    Removes tags from one or more assets.

  • POSTreplace_tags

    Replaces all existing tags on assets with new tags.

Transformation, 5 operations

  • POSTcreate_transformation

    Creates a new named transformation for reuse.

  • DELETEdelete_transformation

    Deletes a transformation and all derived assets using it.

  • GETget_transformation

    Gets detailed information about a specific transformation.

  • GETlist_transformations

    Lists all stored transformations in your Cloudinary account.

  • PUTupdate_transformation

    Updates the definition of an existing transformation.

Upload preset, 5 operations

  • POSTcreate_upload_preset

    Creates a new upload preset with specified settings.

  • DELETEdelete_upload_preset

    Deletes an upload preset.

  • GETget_upload_preset

    Gets detailed configuration of a specific upload preset.

  • GETlist_upload_presets

    Lists all upload presets configured in your account.

  • PUTupdate_upload_preset

    Updates an existing upload preset configuration.

Upload, 2 operations

  • GETget_resource

    Retrieves complete details of a Cloudinary asset including metadata, dimensions, and derived versions.

  • POSTupdate_resource

    Updates attributes of an existing Cloudinary asset.

Derived resource, 1 operation

  • DELETEdelete_derived_resources

    Deletes specific derived (transformed) versions of assets.

Image, 1 operation

  • POSTupload_image

    Uploads an image to Cloudinary. Supports URLs, base64, local files, and cloud storage sources.

Raw, 1 operation

  • POSTupload_raw

    Uploads a raw file (PDF, document, archive) to Cloudinary.

Rename, 1 operation

  • POSTrename_resource

    Renames an asset by changing its public ID.

Usage, 1 operation

  • GETget_usage

    Gets current usage statistics and plan limits for your account.

Video, 1 operation

  • POSTupload_video

    Uploads a video to Cloudinary with optional transformations and organization.

Cloudinary API rate limits

  • 500 requests per hour

Admin API limited to 500 req/hour (free) or 2000 req/hour (paid). Upload API has no rate limits. HTTP 420 returned when rate limited.

These are the limits Cloudinary documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Cloudinary documentation for current values.

Use Cloudinary from Claude Code, Cursor or Codex

Connect Cloudinary in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Cloudinary operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Cloudinary

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Cloudinary once

    Add your Cloudinary connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Cloudinary integration FAQ

What can you do with the Cloudinary integration?
LiveContext exposes 39 operations on Cloudinary, covering asset, folder, tag and transformation. Common uses include tag management, asset organization and folder navigation.
What are the Cloudinary API rate limits?
Cloudinary documents 500 requests per hour. Admin API limited to 500 req/hour (free) or 2000 req/hour (paid). Upload API has no rate limits. HTTP 420 returned when rate limited. Limits are set by Cloudinary and can depend on your plan.

Popular integrations

Browse the whole catalog