Cloudinary Analysis

com.cloudinary由 cloudinary.com 发布官方发布者v0.5.3更新于 Nov 13, 2026

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

已验证Streamable HTTP可网页运行媒体与设计AI 与机器学习

概览

AI 生成的概览

Cloudinary Analysis MCP 服务器让助手对图片执行 AI 分析,包括内容审核、生成说明、打标签、画质与水印检测。

可以做什么
  • 对图片执行 AI 视觉分析,包括打标签、内容审核与通用描述
  • 为素材生成说明文字与文本类分析
  • 调用时尚、商品、文字、人体结构、Google 标签、水印检测等专用分类器
  • 通过 Cloudinary Analyze API 分析外部素材,并按请求的分析类型返回结果
  • 可选动态模式,仅暴露 list_tools、describe_tool_input、execute_tool 等元工具以节省上下文
适用场景
当你希望助手检查 Cloudinary 账户中的图片素材或外部链接,并返回结构化标签、说明、审核标记或画质信号,而不必自己编写 API 调用时适用。
运行要求
可使用远程端点,或通过 npm 包 @cloudinary/analysis-mcp(需 Node.js 20.19.0 及以上)或 Docker 镜像在本地运行。需要 Cloudinary 云名称、API key 与 API secret,可通过 CLOUDINARY_CLOUD_NAME、CLOUDINARY_API_KEY、CLOUDINARY_API_SECRET 环境变量,cloudinary-cloud-name、cloudinary-api-key、cloudinary-api-secret 请求头,或单个 CLOUDINARY_URL 提供;也声明支持 OAuth。部分分析选项需订阅相应附加组件。
安装前请注意
需要提供 Cloudinary API secret(CLOUDINARY_API_SECRET 或 cloudinary-api-secret 请求头),该密钥可访问账户,请勿写入共享配置或日志。Analyze API 处于公开测试阶段,部分分析选项需付费附加组件订阅。提交的图片素材与链接会发送至 Cloudinary 处理。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Cloudinary Analysis,将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.cloudinary%2Fanalysis-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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

来源:README.md,提交 4146c31

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.5.3最新Nov 13, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Cloudinary 集成