Cloudinary Environment Config

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

Manage Cloudinary upload presets, named transformations, mappings, triggers, and streaming profiles.

发布方自己的服务:Cloudinary Analysis

已验证Streamable HTTP可网页运行云端与基础设施媒体与设计

概览

AI 生成的概览

将 AI 助手连接到 Cloudinary 账户,管理命名转换、上传预设、流媒体配置、Webhook 触发器和上传映射。

可以做什么
  • 列出、创建、更新和删除命名转换
  • 列出、查看、创建和更新上传预设
  • 列出、查看、创建和更新用于视频分发的自适应流媒体配置
  • 列出、创建、更新和删除 Webhook 触发器
  • 列出、创建、更新和删除上传文件夹映射
  • 可选启用动态模式,仅暴露用于发现工具的元工具而非全部工具
适用场景
适合在 AI 编程助手内配置 Cloudinary 环境时使用,用自然语言代替控制台或 API 调用来修改转换、预设、流媒体配置、Webhook 或文件夹映射。
运行要求
可使用托管远程端点,或通过 npm 包(需 Node.js 20.19.0 及以上)或 Docker 镜像在本地运行。需要 Cloudinary 云名称、API key 和 API secret,可通过 CLOUDINARY_CLOUD_NAME、CLOUDINARY_API_KEY、CLOUDINARY_API_SECRET 环境变量,cloudinary-api-key、cloudinary-api-secret、cloudinary-cloud-name 请求头,或命令行参数提供;也可用 CLOUDINARY_URL 替代单独变量。远程端点声明使用 OAuth。
安装前请注意
API secret(CLOUDINARY_API_SECRET / cloudinary-api-secret)拥有账户级控制权限,而文档中的配置方式将其以明文命令行参数传入,可能泄露到 shell 历史或配置文件中。相关工具会创建、更新和删除真实的账户配置,如转换、预设、Webhook 触发器和上传映射;删除操作和指向外部服务的 Webhook 地址会立即生效。

安装

在 SourceWeft 中

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

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

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

README

Cloudinary Environment Config MCP Server

Summary

Cloudinary Environment Config MCP Server: Connects AI assistants (including Claude Desktop, Cursor, Gemini, Windsurf, and VS Code) directly to your Cloudinary account. Use natural language to manage named transformations, create and update upload presets, configure adaptive streaming profiles for video delivery, set up event-driven webhooks (triggers), and manage upload folder mappings. Designed for developers who want to control Cloudinary environment configuration without leaving their AI-powered coding environment.

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/environment-config-mcp",    "start",    "--api-key",    "",    "--api-secret",    "",    "--cloud-name",    ""  ]}
Claude Code CLI
bash
claude mcp add CloudinaryEnvConfig -- npx -y @cloudinary/environment-config-mcp start --api-key  --api-secret  --cloud-name 
Gemini
bash
gemini mcp add CloudinaryEnvConfig -- npx -y @cloudinary/environment-config-mcp start --api-key  --api-secret  --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
bash
{  "command": "npx",  "args": [    "@cloudinary/environment-config-mcp",    "start",    "--api-key",    "",    "--api-secret",    "",    "--cloud-name",    ""  ]}
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/environment-config-mcp",    "start",    "--api-key",    "",    "--api-secret",    "",    "--cloud-name",    ""  ]}
Stdio installation via npm To start the MCP server, run:
bash
npx @cloudinary/environment-config-mcp start --api-key  --api-secret  --cloud-name 

For a full list of server arguments, run:

npx @cloudinary/environment-config-mcp --help

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

Available Tools

The MCP server exposes Cloudinary's Environment Configuration API as tools. Use your AI application to discover and invoke the available tools for managing transformations, upload presets, streaming profiles, triggers, and upload mappings.

Usage Examples

Example 1: Manage Named Transformations
1. List transformations: "Show me all named transformations in my account"2. Create transformation: "Create a named transformation 't_thumbnail' with 'c_fill,w_200,h_200'"3. Update transformation: "Update transformation 't_thumbnail' to add sharpen effect"4. Delete transformation: "Delete the transformation named 't_old_banner'"
Example 2: Configure Upload Presets
1. List presets: "Show all my upload presets"2. Create preset: "Create an upload preset named 'user_avatars' with auto tagging enabled"3. Get details: "Show me the configuration for upload preset 'product_images'"4. Update preset: "Update 'user_avatars' preset to use 'square' eager transformation"
Example 3: Manage Streaming Profiles
1. List profiles: "Show all streaming profiles"2. Get profile: "Get details for the 'hd' streaming profile"3. Create profile: "Create a custom streaming profile for 4K video"4. Update profile: "Update the 'mobile' profile with lower bitrate settings"
Example 4: Configure Webhooks (Triggers)
1. List triggers: "Show all webhook triggers configured in my account"2. Create trigger: "Create a webhook trigger for upload events to https://myapp.com/webhooks"3. Update trigger: "Update the webhook URL for trigger [trigger-id]"4. Delete trigger: "Delete the webhook trigger [trigger-id]"
Example 5: Manage Upload Mappings
1. List mappings: "Show all upload folder mappings"2. Create mapping: "Map folder 'blog' to template 'https://example.com/blog/%s'"3. Update mapping: "Update the mapping for 'blog' folder"4. Delete mapping: "Remove the upload mapping for 'old-site' folder"

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/environment-config-mcp.gitcd environment-config-mcp
# Install dependenciesnpm install
# Build the projectnpm run build
# Run locallynpm start

Project Structure

environment-config-mcp/├── src/│   ├── hooks/              # Custom authentication hooks│   ├── mcp-server/         # MCP server implementation│   │   ├── server.ts       # Main server (auto-generated)│   │   └── 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 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

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": {    "CloudinaryEnvConfig": {      "command": "npx",      "args": ["@cloudinary/environment-config-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.
  • list_scopes: Lists the scopes available on the server.

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.

You can combine dynamic mode with scope and tool filters:

jsonc
{  "mcpServers": {    "CloudinaryEnvConfig": {      "command": "npx",      "args": ["@cloudinary/environment-config-mcp", "start", "--mode", "dynamic", "--scope", "admin"],      // ... other server arguments    }  }}

来源:README.md,提交 0b2e044

工具

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

版本历史

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

评分

已满足适用检查项的 85%

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

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

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

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

其他 Cloudinary 集成