# Cloudinary Environment Config MCP server

> Manage Cloudinary named transformations, upload presets, upload mappings, webhook triggers and streaming profiles in natural language.

- Listing: https://mcp.tc/i/cloudinary-environment-config
- Connect: use the server's own URL `https://environment-config.mcp.cloudinary.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: Cloudinary
- Homepage: <https://cloudinary.com/documentation/cloudinary_llm_mcp>
- Docs: <https://cloudinary.com/documentation/cloudinary_llm_mcp>
- Repository: <https://github.com/cloudinary/environment-config-mcp>
- Package: npm `@cloudinary/environment-config-mcp`

## About

Connects an AI assistant to the environment configuration of a Cloudinary account. It can list, create, update and delete named transformations, upload presets, upload mappings, notification triggers (webhooks) and adaptive streaming profiles.

Runs as a hosted streamable HTTP endpoint or as a local npm package (Node.js 20.19.0 or later). The hosted endpoint uses OAuth sign-in to Cloudinary, where you pick the product environment, or you can pass your cloud name, API key and API secret as headers. The local package needs the same three values as environment variables.

## What it can do

- Create, update and delete named transformations
- Manage upload presets
- Configure upload folder mappings
- Set up and test webhook triggers
- Manage adaptive streaming profiles

## Tools (24)

- `list-transformations`: List named and unnamed transformation definitions in the account.
- `get-transformation-details`: Get details of a named or unnamed transformation.
- `create-transformation`: Create a named transformation from a transformation string.
- `update-transformation`: Update an existing transformation definition.
- `delete-transformation`: Delete a named transformation, optionally invalidating derived resources.
- `create-upload-preset`: Create an upload preset with given settings.
- `list-upload-presets`: List all upload presets in the account.
- `get-upload-preset-details`: Get details of one upload preset.
- `update-upload-preset`: Update an upload preset's configuration.
- `delete-upload-preset`: Delete an upload preset.
- `list-upload-mappings`: List upload mappings of folders to URL templates.
- `create-upload-mapping`: Create an upload mapping for a folder.
- `update-upload-mapping`: Change the URL template of a folder mapping.
- `delete-upload-mapping`: Delete the upload mapping for a folder.
- `list-triggers`: List webhook notification triggers in the environment.
- `create-trigger`: Create a webhook trigger for an event type and destination.
- `update-trigger`: Update the callback URL of a trigger.
- `delete-trigger`: Delete a notification trigger.
- `test-trigger`: Test a trigger's filter against sample data.
- `create-streaming-profile`: Create an adaptive streaming profile.
- `list-streaming-profiles`: List built-in and custom streaming profiles.
- `get-streaming-profile`: Get a streaming profile by name.
- `update-streaming-profile`: Modify a streaming profile's configuration.
- `delete-streaming-profile`: Delete a custom profile or revert a built-in one to defaults.

## Example prompts

- "Show me all named transformations in my Cloudinary account"
- "Create an upload preset named user\_avatars with auto tagging enabled"
- "Create a webhook trigger for upload events to https://myapp.com/webhooks"
- "List all streaming profiles and show details for the hd profile"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http cloudinary-environment-config https://environment-config.mcp.cloudinary.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **cloudinary-environment-config** and choose **Authenticate**. A browser window opens for the Cloudinary sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Cloudinary Environment Config** and paste this URL:

```url
https://environment-config.mcp.cloudinary.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when Cloudinary asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Cloudinary%20Environment%20Config&connectorUrl=https%3A%2F%2Fenvironment-config.mcp.cloudinary.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://environment-config.mcp.cloudinary.com/mcp` and click **Add**.

3. Click **Connect** and sign in when Cloudinary asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://environment-config.mcp.cloudinary.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Cloudinary to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=cloudinary-environment-config&config=eyJ1cmwiOiJodHRwczovL2Vudmlyb25tZW50LWNvbmZpZy5tY3AuY2xvdWRpbmFyeS5jb20vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "cloudinary-environment-config": {
      "url": "https://environment-config.mcp.cloudinary.com/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=cloudinary-environment-config&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fenvironment-config.mcp.cloudinary.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"cloudinary-environment-config","type":"http","url":"https://environment-config.mcp.cloudinary.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "cloudinary-environment-config": {
      "serverUrl": "https://environment-config.mcp.cloudinary.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add cloudinary-environment-config --url https://environment-config.mcp.cloudinary.com/mcp
codex mcp login cloudinary-environment-config
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.cloudinary-environment-config]
url = "https://environment-config.mcp.cloudinary.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http cloudinary-environment-config https://environment-config.mcp.cloudinary.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth cloudinary-environment-config` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://environment-config.mcp.cloudinary.com/mcp`.

## Recent changes

- 2026-11-12 23:27 UTC: Tracking started: 24 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/cloudinary-environment-config#history (Atom feed: https://mcp.tc/i/cloudinary-environment-config/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.6.4
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-12
- Updated: 2026-11-12

---
Source: https://mcp.tc/i/cloudinary-environment-config (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
