Cloudinary Analysis

com.cloudinaryPublished by cloudinary.comOfficial publisherv0.5.3Updated Nov 13, 2026

Run AI-powered analysis on images including moderation, captioning, tagging, and more.

VerifiedStreamable HTTPWeb executableMedia & DesignAI & ML

Overview

AI-generated overview

Cloudinary Analysis MCP server lets an assistant run AI-powered analysis on images: moderation, captioning, tagging, quality and watermark checks.

What you can do
  • Run AI vision analysis on images, including tagging, moderation and general description
  • Generate captions and text-based analysis of assets
  • Apply specialized classifiers such as fashion, shop, text, human anatomy, Google tagging and watermark detection
  • Analyze external assets through Cloudinary's Analyze API and return results for the requested analysis type
  • Optionally expose only meta-tools (list_tools, describe_tool_input, execute_tool) in dynamic mode to save context
When to use it
Useful when you want an assistant to inspect image assets in a Cloudinary account or external URLs and return structured labels, captions, moderation flags or quality signals without writing API calls yourself.
Requirements
Either the remote endpoint or a local process via npm package @cloudinary/analysis-mcp (Node.js 20.19.0 or later) or the Docker image. Requires a Cloudinary cloud name plus API key and secret, supplied as CLOUDINARY_CLOUD_NAME, CLOUDINARY_API_KEY and CLOUDINARY_API_SECRET, as the cloudinary-cloud-name, cloudinary-api-key and cloudinary-api-secret headers, or as a single CLOUDINARY_URL. OAuth is also declared. Analysis options require an active subscription to the relevant add-on.
Before you install
You must supply a Cloudinary API secret (CLOUDINARY_API_SECRET or the cloudinary-api-secret header), which grants account access; keep it out of shared configs and logs. The Analyze API is a public beta and some analysis options require paid add-on subscriptions. Image assets and URLs you submit are sent to Cloudinary for processing.

Installation

In SourceWeft

  1. Open Cloudinary Analysis in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.cloudinary%2Fanalysis-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cloudinary-analysis": {
      "type": "http",
      "url": "https://analysis.mcp.cloudinary.com/mcp"
    }
  }
}

README

Cloudinary Analysis MCP Server

Summary

Analyze API (Beta): Use the Analyze API to analyze any external asset and return details based on the type of analysis requested.

Currently supports the following analysis options:

Notes:

  • The Analyze API is currently in development and is available as a Public Beta, which means we value your feedback, so please feel free to share any thoughts with us.
  • The analysis options require an active subscription to the relevant add-on. Learn more about registering for add-ons.

The API supports both Basic Authentication using your Cloudinary API Key and API Secret (which can be found on the Dashboard page of your Cloudinary Console) or OAuth2 (Contact support for more information regarding OAuth).

Table of Contents

Installation

The MCP server requires Node.js 20.19.0 or later.

Claude Desktop

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

[Install MCP Server]

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:
json
{  "command": "npx",  "args": [    "@cloudinary/analysis-mcp",    "start",    "--cloud-name",    "CLOUD_NAME",    "--api-key",    "",    "--api-secret",    "",    "--o-auth2",    ""  ]}
Claude Code CLI
bash
claude mcp add CloudinaryAnalysis -- npx -y @cloudinary/analysis-mcp start --cloud-name CLOUD_NAME --api-key  --api-secret  --o-auth2 
Gemini
bash
gemini mcp add CloudinaryAnalysis -- npx -y @cloudinary/analysis-mcp start --cloud-name CLOUD_NAME --api-key  --api-secret  --o-auth2 
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
bash
{  "command": "npx",  "args": [    "@cloudinary/analysis-mcp",    "start",    "--cloud-name",    "CLOUD_NAME",    "--api-key",    "",    "--api-secret",    "",    "--o-auth2",    ""  ]}
VS Code

[Install in VS Code]

Or manually:

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
bash
{  "command": "npx",  "args": [    "@cloudinary/analysis-mcp",    "start",    "--cloud-name",    "CLOUD_NAME",    "--api-key",    "",    "--api-secret",    "",    "--o-auth2",    ""  ]}
Stdio installation via npm To start the MCP server, run:
bash
npx @cloudinary/analysis-mcp start --cloud-name CLOUD_NAME --api-key  --api-secret  --o-auth2 

For a full list of server arguments, run:

npx @cloudinary/analysis-mcp --help

Progressive Discovery

MCP servers with many tools can bloat LLM context windows, leading to increased token usage and tool confusion. Dynamic mode solves this by exposing only a small set of meta-tools that let agents progressively discover and invoke tools on demand.

To enable dynamic mode, pass the --mode dynamic flag when starting your server:

jsonc
{  "mcpServers": {    "CloudinaryAnalysis": {      "command": "npx",      "args": ["@cloudinary/analysis-mcp", "start", "--mode", "dynamic"],      // ... other server arguments    }  }}

In dynamic mode, the server registers only the following meta-tools instead of every individual tool:

  • list_tools: Lists all available tools with their names and descriptions.
  • describe_tool_input: Returns the input schema for one or more tools by name.
  • execute_tool: Executes a tool by name with its arguments.

This approach significantly reduces the number of tokens sent to the LLM on each request, which is especially useful for servers with a large number of tools.

Configuration

Environment Variables

The MCP server supports the following environment variables:

VariableDescriptionRequired
CLOUDINARY_CLOUD_NAMEYour Cloudinary cloud nameYes
CLOUDINARY_API_KEYYour Cloudinary API keyYes
CLOUDINARY_API_SECRETYour Cloudinary API secretYes
CLOUDINARY_URLComplete Cloudinary URL (alternative to individual vars)No

CLOUDINARY_URL Format

You can use a single CLOUDINARY_URL instead of individual variables:

bash
CLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME

Authentication

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

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

Development

Building from Source

Prerequisites

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

Build Steps

bash
# Clone the repositorygit clone https://github.com/cloudinary/analysis-mcp.gitcd analysis-mcp
# Install dependenciesnpm install
# Build the projectnpm run build
# Run locallynpm start

Contributions

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

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

Source: README.md at commit 4146c31

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.5.3LatestNov 13, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

Other Cloudinary integrations