@cloudinary/structured-metadata-mcp
v0.3.1
Published
<!-- Start Summary [summary] --> ## Summary
Readme
Cloudinary Structured Metadata MCP Server
Summary
Table of Contents
Installation
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.
Or manually:
- Open Cursor Settings
- Select Tools and Integrations
- Select New MCP Server
- If the configuration file is empty paste the following JSON into the MCP Server Configuration:
{
"mcpServers": {
"CloudinarySMD": {
"command": "npx",
"args": [
"@cloudinary/structured-metadata-mcp",
"start",
"--server-index",
"...",
"--region",
"...",
"--api-host",
"...",
"--api-key",
"...",
"--api-secret",
"...",
"--oauth2",
"...",
"--cloud-name",
"..."
]
}
}
}claude mcp add @cloudinary/structured-metadata-mcp npx @cloudinary/structured-metadata-mcp start -- --server-index ... --region ... --api-host ... --api-key ... --api-secret ... --oauth2 ... --cloud-name ...Refer to Official Windsurf documentation for latest information
- Open Windsurf Settings
- Select Cascade on left side menu
- Click on
Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account) - Click on
View raw configto open up the mcp configuration file. - If the configuration file is empty paste the full json
{
"mcpServers": {
"CloudinarySMD": {
"command": "npx",
"args": [
"@cloudinary/structured-metadata-mcp",
"start",
"--server-index",
"...",
"--region",
"...",
"--api-host",
"...",
"--api-key",
"...",
"--api-secret",
"...",
"--oauth2",
"...",
"--cloud-name",
"..."
]
}
}
}Refer to Official VS Code documentation for latest information
- Open Command Palette
- Search and open
MCP: Open User Configuration. This should open mcp.json file - If the configuration file is empty paste the full json
{
"mcpServers": {
"CloudinarySMD": {
"command": "npx",
"args": [
"@cloudinary/structured-metadata-mcp",
"start",
"--server-index",
"...",
"--region",
"...",
"--api-host",
"...",
"--api-key",
"...",
"--api-secret",
"...",
"--oauth2",
"...",
"--cloud-name",
"..."
]
}
}
}You need to do the following
- Open claude Desktop
- Open left hand side pane, then click on your Username
- Go to
Settings - Go to
Developertab (on the left hand side) - Click on
Edit ConfigPaste the following config in the configuration
{
"mcpServers": {
"CloudinarySMD": {
"command": "npx",
"args": [
"@cloudinary/structured-metadata-mcp",
"start",
"--server-index",
"...",
"--region",
"...",
"--api-host",
"...",
"--api-key",
"...",
"--api-secret",
"...",
"--oauth2",
"...",
"--cloud-name",
"..."
]
}
}
}npx @cloudinary/structured-metadata-mcp start --server-index ... --region ... --api-host ... --api-key ... --api-secret ... --oauth2 ... --cloud-name ...For a full list of server arguments, run:
npx @cloudinary/structured-metadata-mcp --helpConfiguration
Environment Variables
The MCP server supports the following environment variables:
| Variable | Description | Required |
|----------|-------------|----------|
| CLOUDINARY_CLOUD_NAME | Your Cloudinary cloud name | Yes |
| CLOUDINARY_API_KEY | Your Cloudinary API key | Yes |
| CLOUDINARY_API_SECRET | Your Cloudinary API secret | Yes |
| CLOUDINARY_URL | Complete Cloudinary URL (alternative to individual vars) | No |
CLOUDINARY_URL Format
You can use a single CLOUDINARY_URL instead of individual variables:
CLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAMEAuthentication
The MCP server uses your Cloudinary API key and secret for authentication:
{
"env": {
"CLOUDINARY_CLOUD_NAME": "demo",
"CLOUDINARY_API_KEY": "123456789012345",
"CLOUDINARY_API_SECRET": "abcdefghijklmnopqrstuvwxyz12"
}
}Available Tools
The MCP server exposes Cloudinary's Structured Metadata API as tools. Use your AI application to discover and invoke the available tools for managing metadata fields and rules.
Usage Examples
Example 1: Manage Metadata Fields
1. List fields: "Show me all metadata fields in my account"
2. Create field: "Create a metadata field named 'category' of type 'enum' with values 'product,service,other'"
3. Get field: "Get details for the metadata field 'category'"
4. Update field: "Update the 'category' field to add a new value 'subscription'"
5. Delete field: "Delete the metadata field 'old_field'"Example 2: Manage Field Datasources
1. Search datasource: "Search for values in the 'category' field datasource"
2. Update datasource: "Add a new value 'enterprise' to the 'category' field datasource"
3. Delete datasource entry: "Remove the value 'old_value' from the 'category' field"
4. Restore datasource: "Restore a deleted datasource entry for field 'category'"Example 3: Manage Metadata Rules
1. List rules: "Show all metadata rules configured in my account"
2. Create rule: "Create a metadata rule to auto-tag assets in folder 'products' with category 'product'"
3. Update rule: "Update metadata rule [rule-id] to change the target folder"
4. Delete rule: "Delete metadata rule [rule-id]"Example 4: Reorder Metadata Fields
1. Reorder single field: "Move the 'priority' metadata field to position 2"
2. Reorder multiple fields: "Reorder metadata fields: set 'category' to position 1, 'priority' to position 2"Development
Building from Source
Prerequisites
- Node.js v20 or higher
- npm, pnpm, bun, or yarn
Build Steps
# Clone the repository
git clone https://github.com/cloudinary/structured-metadata-mcp.git
cd structured-metadata-mcp
# Install dependencies
npm install
# Build the project
npm run build
# Run locally
npm startProject Structure
structured-metadata-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 configurationContributions
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.
