MediaFlows MCP server

This page provides setup instructions and practical guidance for using the MediaFlows Model Context Protocol (MCP) server with MCP clients such as Cursor and Claude Desktop.

See also: Cloudinary MCP servers and LLM tools

Configure your MCP client to use the MediaFlows MCP server

Use the following configuration in your MCP client:

The following instructions explain how to set up this configuration in Cursor and Claude Desktop. If you're using a different MCP client, refer to its documentation.

In Cursor:

1. Go to Cursor Settings -> MCP Tools -> New MCP Server.
2. In the mcp.json file, if you already have an MCP server set up, copy and paste the "mediaflows" configuration into"mcpServers". Otherwise, copy and paste the entire configuration above.
3. Replace api_key, api_secret and cloud_name with your Cloudinary product environment API key, API secret, and cloud name.
   Find your product environment credentials in your console.

Alternatively, you can click the Add to Cursor button, then add your credentials by editing the config:

In Claude Desktop:

1. Go to Claude -> Settings..., click Developer and Edit Config.
2. In the claude_desktop_config.json file, if you already have an MCP server set up, copy and paste the "mediaflows" configuration into"mcpServers". Otherwise, copy and paste the entire configuration above.
3. Replace api_key, api_secret and cloud_name with your Cloudinary product environment API key, API secret, and cloud name.
   Find your product environment credentials in your console.
4. Restart Claude Desktop.

What can I use the MediaFlows MCP server for?

Once the MediaFlows MCP server is configured and enabled in your MCP client, you can ask it about the flows in your Cloudinary MediaFlows environment, build new automations, and help you to debug your automations.

Here are some usage examples:

• What automations do I have in my environment that work when I upload an image?
• What automations change the Akeneo Status metadata field in my environment?
• What actions can you automate for me?
• When an asset is uploaded to Cloudinary and has metadata "product" equal to true, check if the image contains two visible soccer shoes. If it does, add a tag to state two shoes. In case it doesn't, send the image to manual moderation and send an email to moderation@company.com.
• Create an automation so that when the metadata field called "category" changes to "product", it generates alt text, stores it in the "description" metadata, moves the asset to the products folder, and sends an email to approval@company.com.
• When metadata status changes to expired, add a tag, "expired", and make the asset private.

Tips and considerations

• Currently, the MCP server tools support PowerFlows but not EasyFlows.
• The tool creates flows as inactive so that you can review them before enabling.
• Currently, the MCP server tools don't allow you to modify existing automations.
• If you want to create a new flow, it's best to specify "Create a MediaFlows flow..."
• MCP servers in general aren't always consistent. A prompt or question you write today may yield different results tomorrow.
• Use the most advanced LLM model available. The better the LLM model, the better your results will be.