[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_107":108},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module '@cloudinary/asset-management-mcp' is not configured","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":26,"_34":-5,"_35":36,"_37":-5,"_38":-5,"_39":40,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52,"_53":54,"_55":48,"_56":57,"_58":59,"_60":-5,"_61":-5,"_62":-5,"_63":-5,"_64":65,"_66":67,"_68":69,"_70":71,"_72":73,"_74":-5,"_75":-5,"_76":77,"_78":48,"_79":-5,"_80":57,"_81":82,"_83":84,"_85":86,"_87":88,"_89":90,"_91":92},"apiUrl","https://odel.app/api","creator","cloudinary","moduleId","asset-management-mcp","@cloudinary/asset-management-mcp","displayName","Cloudinary Asset Management","tagline","Upload, organize, search, and transform images, videos, and files with AI-powered tools.","iconKey","https://avatars.githubusercontent.com/u/1460763?v=4","category","dev-tools","status","published","metaDescription","metaKeywords","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://asset-management.mcp.cloudinary.com/mcp\",\"transport\":\"streamable-http\",\"authType\":\"headers\",\"requiredSecrets\":[\"CLOUDINARY_CLOUD_NAME\",\"CLOUDINARY_API_KEY\",\"CLOUDINARY_API_SECRET\"]}","pricingModel","free","creatorUserId","system:external-import","createdAt",1781363405000,"updatedAt",1781499599000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.cloudinary%2Fasset-management-mcp","sourceVerified",true,"importedAt","upstreamStars",0,"upstreamUpdatedAt",1781084052000,"detectedTransport","detectedAuthType","probeStatus","lastProbedAt","githubRepoUrl","https://github.com/cloudinary/asset-management-mcp","githubRepoFullName","cloudinary/asset-management-mcp","releaseId","ext-cloudinary-asset-management-mcp","version","0.8.1","descriptionMarkdown","# Cloudinary Asset Management MCP Server\n\n\n\n\n## Summary\n\n\n\n\n\n## Table of Contents\n\n* [Cloudinary Asset Management MCP Server](#cloudinary-asset-management-mcp-server)\n * [Installation](#installation)\n * [Configuration](#configuration)\n * [Authentication](#authentication)\n * [Available Tools](#available-tools)\n * [Custom Tools](#custom-tools)\n * [Progressive Discovery](#progressive-discovery)\n* [Development](#development)\n * [Building from Source](#building-from-source)\n * [Contributions](#contributions)\n\n\n\n\n## Installation\n\n

Claude Desktop

\n\nInstall the MCP server as a Desktop Extension using the pre-built [`mcp-server.mcpb`](https://github.com/cloudinary/asset-management-mcp/releases/download/v0.9.3/mcp-server.mcpb) file:\n\nSimply drag and drop the [`mcp-server.mcpb`](https://github.com/cloudinary/asset-management-mcp/releases/download/v0.9.3/mcp-server.mcpb) file onto Claude Desktop to install the extension.\n\nThe MCP bundle package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.\n\n> [!NOTE]\n> MCP bundles provide a streamlined way to package and distribute MCP servers. Learn more about [Desktop Extensions](https://www.anthropic.com/engineering/desktop-extensions).\n\n

\n\n

Cursor

\n\n[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](cursor://anysphere.cursor-deeplink/mcp/install?name=CloudinaryAssetMgmt&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyJAY2xvdWRpbmFyeS9hc3NldC1tYW5hZ2VtZW50LW1jcCIsInN0YXJ0IiwiLS1hcGkta2V5IiwiIiwiLS1hcGktc2VjcmV0IiwiIiwiLS1jbG91ZC1uYW1lIiwiIl19)\n\nOr manually:\n\n1. Open Cursor Settings\n2. Select Tools and Integrations\n3. Select New MCP Server\n4. If the configuration file is empty paste the following JSON into the MCP Server Configuration:\n\n```json\n{\n \"command\": \"npx\",\n \"args\": [\n \"@cloudinary/asset-management-mcp\",\n \"start\",\n \"--api-key\",\n \"\",\n \"--api-secret\",\n \"\",\n \"--cloud-name\",\n \"\"\n ]\n}\n```\n\n

\n\n

Claude Code CLI

\n\n```bash\nclaude mcp add CloudinaryAssetMgmt -- npx -y @cloudinary/asset-management-mcp start --api-key --api-secret --cloud-name \n```\n\n

Gemini

\n\n```bash\ngemini mcp add CloudinaryAssetMgmt -- npx -y @cloudinary/asset-management-mcp start --api-key --api-secret --cloud-name \n```\n\n

Windsurf

\n\nRefer to [Official Windsurf documentation](https://docs.windsurf.com/windsurf/cascade/mcp#adding-a-new-mcp-plugin) for latest information\n\n1. Open Windsurf Settings\n2. Select Cascade on left side menu\n3. Click on `Manage MCPs`. (To Manage MCPs you should be signed in with a Windsurf Account)\n4. Click on `View raw config` to open up the mcp configuration file.\n5. If the configuration file is empty paste the full json\n\n```bash\n{\n \"command\": \"npx\",\n \"args\": [\n \"@cloudinary/asset-management-mcp\",\n \"start\",\n \"--api-key\",\n \"\",\n \"--api-secret\",\n \"\",\n \"--cloud-name\",\n \"\"\n ]\n}\n```\n

VS Code

\n\n[![Install in VS Code](https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20CloudinaryAssetMgmt%20MCP&color=0098FF)](vscode://ms-vscode.vscode-mcp/install?name=CloudinaryAssetMgmt&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyJAY2xvdWRpbmFyeS9hc3NldC1tYW5hZ2VtZW50LW1jcCIsInN0YXJ0IiwiLS1hcGkta2V5IiwiIiwiLS1hcGktc2VjcmV0IiwiIiwiLS1jbG91ZC1uYW1lIiwiIl19)\n\nOr manually:\n\nRefer to [Official VS Code documentation](https://code.visualstudio.com/api/extension-guides/ai/mcp) for latest information\n\n1. Open [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)\n1. Search and open `MCP: Open User Configuration`. This should open mcp.json file\n2. If the configuration file is empty paste the full json\n\n```bash\n{\n \"command\": \"npx\",\n \"args\": [\n \"@cloudinary/asset-management-mcp\",\n \"start\",\n \"--api-key\",\n \"\",\n \"--api-secret\",\n \"\",\n \"--cloud-name\",\n \"\"\n ]\n}\n```\n\n

Stdio installation via npm

\nTo start the MCP server, run:\n\n```bash\nnpx @cloudinary/asset-management-mcp start --api-key --api-secret --cloud-name \n```\n\nFor a full list of server arguments, run:\n\n```\nnpx @cloudinary/asset-management-mcp --help\n```\n\n

\n\n\n## Configuration\n\n### Environment Variables\n\nThe MCP server supports the following environment variables:\n\n| Variable | Description | Required |\n|----------|-------------|----------|\n| `CLOUDINARY_CLOUD_NAME` | Your Cloudinary cloud name | Yes |\n| `CLOUDINARY_API_KEY` | Your Cloudinary API key | Yes |\n| `CLOUDINARY_API_SECRET` | Your Cloudinary API secret | Yes |\n| `CLOUDINARY_URL` | Complete Cloudinary URL (alternative to individual vars) | No |\n| `CLOUDINARY_COLLECT_HEADERS` | Collect API response headers (see below) | No |\n| `CLOUDINARY_MCP_APPS` | Override MCP Apps default (see [MCP Apps](#mcp-apps)) | No |\n\n### CLOUDINARY_URL Format\n\nYou can use a single `CLOUDINARY_URL` instead of individual variables:\n\n```bash\nCLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME\n```\n\n### Response Header Collection\n\nYou can configure the server to include Cloudinary API response headers (such as `x-request-id` and rate limit info) in tool output. This is useful for debugging and monitoring.\n\nSet `CLOUDINARY_COLLECT_HEADERS` to control which headers are collected:\n\n```bash\n# Collect all response headers\nCLOUDINARY_COLLECT_HEADERS=true\n\n# Collect specific headers by exact name (comma-separated)\nCLOUDINARY_COLLECT_HEADERS=x-request-id,x-featureratelimit-limit,x-featureratelimit-remaining\n\n# Mix exact names, prefix matching, and regex matching\nCLOUDINARY_COLLECT_HEADERS=x-request-id,prefix:x-featureratelimit-\n```\n\n#### Header matching specs\n\nEach entry in the comma-separated list is matched against response header names:\n\n| Format | Example | Behaviour |\n|--------|---------|-----------|\n| exact name | `x-request-id` | matches only `x-request-id` |\n| `prefix:` | `prefix:x-featureratelimit-` | matches any header starting with `x-featureratelimit-` |\n| `regex:` | `regex:ratelimit` | matches any header whose name contains `ratelimit` |\n\nYou can also set this via the `CLOUDINARY_URL` query parameter:\n\n```bash\nCLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME?collect_headers=true\n```\n\nWhen enabled, collected headers appear in an `_headers` field in the tool response. When not set, no headers are collected and responses are unchanged.\n\n### MCP Apps\n\nThe server can expose interactive MCP UI **Apps** (spec-aligned with `io.modelcontextprotocol/ui`) that hosts can render alongside tool results — for example, an asset gallery for list results, a single-asset detail view, and an upload UI.\n\nApps are **enabled by default**. Use the `--mcp-apps` flag (available on both `start` and `serve`) or the `CLOUDINARY_MCP_APPS` environment variable to override this behaviour:\n\n| Value | Effect |\n|-------|--------|\n| unset | Default — **all apps enabled** |\n| bare `--mcp-apps` (no value), `all`, or `true` | Enable every app (same as default) |\n| `none` or `false` | Disable every app (kill-switch) |\n| comma-separated subset, e.g. `asset-gallery,asset-details` | Enable only the listed apps |\n\nAvailable app names: `asset-gallery`, `asset-details`, `asset-upload`.\n\n```bash\n# Disable all apps\nnpx @cloudinary/asset-management-mcp serve --mcp-apps none\n\n# Enable only the gallery\nnpx @cloudinary/asset-management-mcp start --mcp-apps asset-gallery\n\n# Disable via env var\nCLOUDINARY_MCP_APPS=none npx @cloudinary/asset-management-mcp start\n```\n\nPrecedence: CLI flag > environment variable > built-in default.\n\n\n\n## Authentication\n\nThe MCP server uses your Cloudinary API key and secret for authentication:\n\n```json\n{\n \"env\": {\n \"CLOUDINARY_CLOUD_NAME\": \"demo\",\n \"CLOUDINARY_API_KEY\": \"123456789012345\",\n \"CLOUDINARY_API_SECRET\": \"abcdefghijklmnopqrstuvwxyz12\"\n }\n}\n```\n\n\n\n## Available Tools\n\nThe MCP server exposes Cloudinary's Asset Management API as tools. Use your AI application to discover and invoke the available tools for uploading, managing, searching, and transforming your media assets.\n\n### Usage Examples\n\n#### Example 1: Upload and Transform an Image\n\n```yaml\n1. Upload a local image: \"Upload file:///Users/me/photo.jpg to Cloudinary as 'hero-image'\"\n2. Transform it: \"Transform asset 'hero-image' with transformations 'c_fill,w_800,h_600/e_sharpen'\"\n3. Get details: \"Show me details for asset with ID [asset-id]\"\n```\n\n#### Example 2: Search and Organize Assets\n\n```yaml\n1. Search for images: \"Find all images with tag 'product' uploaded in the last 7 days\"\n2. Create folder: \"Create a new folder called 'summer-2024-products'\"\n3. List assets: \"Show me all video assets in the 'marketing' folder\"\n```\n\n#### Example 3: Generate Archive\n\n```yaml\n1. Get transformation docs: \"Show me the Cloudinary transformation reference\"\n2. Apply transformations: \"Transform 'banner' asset with 'c_scale,w_1200/f_auto,q_auto'\"\n3. Create archive: \"Generate a ZIP archive of all images with tag 'export-ready'\"\n```\n\n#### Example 4: Asset Management Workflow\n\n```yaml\n1. Upload multiple files: \"Upload all images from folder /assets/new-products/\"\n2. Add tags: \"Update asset [asset-id] and add tags 'featured,homepage'\"\n3. Get usage stats: \"Show my Cloudinary account usage statistics\"\n```\n\n## Custom Tools\n\nThis MCP server includes two powerful custom tools:\n\n### `get-tx-reference`\n\nRetrieves the complete Cloudinary transformation reference documentation.\n\n**When to use:**\n\n- Before creating or modifying transformations\n- When user asks about image/video effects, resizing, cropping, filters\n\n**Example:**\n\n```sh\nUse get-tx-reference to learn about available transformations\n```\n\n### `transform-asset`\n\nApplies transformations to existing assets using Cloudinary's explicit API.\n\n**Parameters:**\n\n- `publicId` - The asset's public ID\n- `transformations` - Transformation string (e.g., `c_fill,w_300,h_200`)\n- `resourceType` - Type: `image`, `video`, or `raw` (default: `image`)\n- `invalidate` - Invalidate CDN cache (default: `false`)\n\n**Example:**\n\n```sh\nTransform asset \"sample\" with transformations \"c_fill,w_500,h_500/e_sepia\"\n```\n\n\n## Progressive Discovery\n\nMCP 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.\n\nTo enable dynamic mode, pass the `--mode dynamic` flag when starting your server:\n\n```jsonc\n{\n \"mcpServers\": {\n \"CloudinaryAssetMgmt\": {\n \"command\": \"npx\",\n \"args\": [\"@cloudinary/asset-management-mcp\", \"start\", \"--mode\", \"dynamic\"],\n // ... other server arguments\n }\n }\n}\n```\n\nIn dynamic mode, the server registers only the following meta-tools instead of every individual tool:\n\n- **`list_tools`**: Lists all available tools with their names and descriptions.\n- **`describe_tool_input`**: Returns the input schema for one or more tools by name.\n- **`execute_tool`**: Executes a tool by name with its arguments.\n- **`list_scopes`**: Lists the scopes available on the server.\n\nThis 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.\n\nYou can combine dynamic mode with scope and tool filters:\n\n```jsonc\n{\n \"mcpServers\": {\n \"CloudinaryAssetMgmt\": {\n \"command\": \"npx\",\n \"args\": [\"@cloudinary/asset-management-mcp\", \"start\", \"--mode\", \"dynamic\", \"--scope\", \"admin\"],\n // ... other server arguments\n }\n }\n}\n```\n\n\n# Development\n\n## Building from Source\n\n### Prerequisites\n\n- Node.js v20 or higher\n- npm, pnpm, bun, or yarn\n\n### Build Steps\n\n```bash\n# Clone the repository\ngit clone https://github.com/cloudinary/asset-management-mcp.git\ncd asset-management-mcp\n\n# Install dependencies\nnpm install\n\n# Build the project\nnpm run build\n\n# Run locally\nnpm start\n```\n\n### Project Structure\n\n```ini\nasset-management-mcp/\n├── src/\n│ ├── hooks/ # SDK hooks (manual)\n│ │ ├── cloudinaryAuthHook.ts # Auth & file:// handling\n│ │ ├── customHeadersHook.ts # Inject custom request headers\n│ │ ├── responseHeadersHook.ts # Collect response headers\n│ │ ├── userAgentHook.ts # Build User-Agent string\n│ │ └── registration.ts # Hook registration\n│ ├── mcp-server/ # MCP server implementation\n│ │ ├── server.ts # Main server (auto-generated)\n│ │ ├── server.extensions.ts # Custom tools & app wiring (manual)\n│ │ ├── tools/ # Generated tool wrappers\n│ │ └── apps/ # MCP UI Apps (manual)\n│ │ ├── config.ts # App registry & --mcp-apps parsing\n│ │ ├── cli-flag.ts # stricli flag definition\n│ │ ├── extensions.ts # Resource-template registration\n│ │ ├── uri.ts # App URI helpers / tool-name injection\n│ │ ├── tool-hooks.ts # Per-tool app hooks\n│ │ ├── app-shared.ts # Shared app utilities\n│ │ ├── asset-gallery-app.ts # List results gallery UI\n│ │ ├── asset-details-app.ts # Single-asset detail UI\n│ │ └── asset-upload-app.ts # Upload UI\n│ ├── funcs/ # API function implementations\n│ └── models/ # Type definitions\n├── .github/\n│ └── workflows/ # CI/CD workflows\n└── .speakeasy/ # Speakeasy configuration\n```\n\n## Contributions\n\nWhile we value contributions to this MCP Server, most of the code is generated programmatically from the Cloudinary API spec. Any manual changes to generated files will be overwritten on the next generation — please direct your changes to the manual extension points below.\n\n**What you can contribute:**\n\n- Custom tools and server wiring in `src/mcp-server/server.extensions.ts`\n- MCP UI Apps in `src/mcp-server/apps/` (gallery, details, upload, and new apps)\n- SDK hooks in `src/hooks/` (auth, custom headers, response headers, user agent)\n- Documentation improvements (this README, JSDoc on manual files)\n- Bug reports and feature requests\n\n**Generated files (do not edit):**\n\n- `src/mcp-server/server.ts`\n- `src/mcp-server/tools/*.ts`\n- `src/funcs/*.ts`\n- `src/models/*.ts`\n\nWhen touching generated files is unavoidable, prefer updating the upstream spec or Speakeasy configuration in `.speakeasy/` so the change survives regeneration.\n\nWe 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.\n\n---\n\n### MCP Server Created by [Speakeasy](https://www.speakeasy.com/?utm_source=asset-management-mcp&utm_campaign=mcp-typescript)\n\n\n","changelogMarkdown","videoKey","requiredSecretsJson","[\"CLOUDINARY_CLOUD_NAME\",\"CLOUDINARY_API_KEY\",\"CLOUDINARY_API_SECRET\"]","publishedAt","priceCents","trialDays","categoryDisplayName","Developer Tools","upstream",{"_98":99,"_100":101,"_102":103,"_104":105,"_106":-5},"requiredSecrets",[95,96,97],"tags",[],"assets",[],"stats",{"_93":57,"_94":57},"ratingAvg","reviewCount","CLOUDINARY_CLOUD_NAME","CLOUDINARY_API_KEY","CLOUDINARY_API_SECRET","topics",[],"license","MIT","language","TypeScript","registryName","io.github.cloudinary/asset-management-mcp","homepage","ENV",{"_109":110,"_111":112,"_113":114},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]