How to connect Cloudinary to OpenClaw
Connect Cloudinary to OpenClaw with ClawLink: paste your Cloudinary key once and 108 tools work from chat. No MCP server to run, nothing stored on your machine.
CloudinaryAPI KEYMCPCloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN.. Once connected, OpenClaw can read and act on Cloudinary from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Cloudinary access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Cloudinary setup: install one ClawHub skill, connect Cloudinary in the browser, and OpenClaw can call real Cloudinary actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Cloudinary skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Cloudinary" (hith3sh/cloudinary-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/cloudinary-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Cloudinary.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Cloudinary
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Cloudinary?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Cloudinary in the ClawLink dashboard — paste your Cloudinary API key once.
Verify the connection by asking OpenClaw:
Use Cloudinary to activate live stream and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Cloudinary is connected in the dashboard, that agent calls the same 108 Cloudinary tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Cloudinary MCP for OpenClaw
Looking for a Cloudinary MCP server for OpenClaw? ClawLink connects Cloudinary to OpenClaw and exposes 108 Cloudinary tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Cloudinary integration works the same way.
What the OpenClaw Cloudinary integration can do
108 Cloudinary tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 108.
30 of 108 Cloudinary tools for OpenClaw
| Tool | What it does |
|---|---|
Activate live stream cloudinary_activate_live_stream | Manually activate a Cloudinary live stream |
Create asset relations by asset ID cloudinary_create_asset_relations_by_asset_id | Add related assets by asset ID |
Create asset relations by public ID cloudinary_create_asset_relations_by_public_id | Create relations between assets by public ID |
Create folder cloudinary_create_folder | Create a new asset folder |
Get adaptive streaming profiles cloudinary_get_adaptive_streaming_profiles | List adaptive streaming profiles |
Get analysis task status cloudinary_get_analysis_task_status | Get the status of an analysis task |
Get config cloudinary_get_config | Get product environment config details |
Get live stream cloudinary_get_live_stream | Get details of a single live stream by ID |
Get live stream output cloudinary_get_live_stream_output | Get details of a single live stream output |
Get live stream outputs cloudinary_get_live_stream_outputs | Get a list of live stream outputs |
Get live streams cloudinary_get_live_streams | Get a list of live streams from Cloudinary |
Get metadata field by ID cloudinary_get_metadata_field_by_id | Get a single metadata field definition by external ID |
Get resource by asset ID cloudinary_get_resource_by_asset_id | Get Resource by Asset ID |
Get resource by public ID cloudinary_get_resource_by_public_id | Get details of a single resource by public ID |
Get resources by asset folder cloudinary_get_resources_by_asset_folder | List assets stored directly in a specified folder |
Get resources by context cloudinary_get_resources_by_context | Retrieve assets with a specified contextual metadata key/value |
Get resources in moderation cloudinary_get_resources_in_moderation | Retrieve assets in a moderation queue by status |
Get root folders cloudinary_get_root_folders | List all root folders in the product environment |
Get streaming profile details cloudinary_get_streaming_profile_details | Get details of a single streaming profile by name |
Get tags cloudinary_get_tags | List all tags used for a specified resource type |
Get transformation cloudinary_get_transformation | Retrieve details of a specific transformation |
Get transformations cloudinary_get_transformations | List all transformations (named and unnamed) |
Get triggers cloudinary_get_triggers | List all webhook triggers for event types in your environment |
Get upload mapping details cloudinary_get_upload_mapping_details | Retrieve details of a single upload mapping by folder |
Get upload mappings cloudinary_get_upload_mappings | List all upload mappings |
Get upload preset cloudinary_get_upload_preset | Retrieve details of a single upload preset by name |
Get usage cloudinary_get_usage | Get product environment usage details |
Get video views cloudinary_get_video_views | Get video analytics views from Cloudinary |
List images cloudinary_list_images | List image assets from Cloudinary |
List metadata fields cloudinary_list_metadata_fields | List all structured metadata fields defined in your Cloudinary product environment |
Try it: find the Cloudinary tool you need
Browse the 30 Cloudinary tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Cloudinary to activate live stream and walk me through the result in plain English.
Create it in Cloudinary for me, then confirm the important fields before you finish.
Create it in Cloudinary for me, then confirm the important fields before you finish.
Create it in Cloudinary for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cloudinary working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Cloudinary API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cloudinary account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Cloudinary. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Cloudinary actions to the runtime in a format your agent can reliably use. | 108 tools for Cloudinary are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Cloudinary to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Cloudinary in the browser, and the 108 tools above work from chat. There is no SDK and no config file, and the Cloudinary key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Cloudinary skill but can't call the tools
The ClawHub skill teaches OpenClaw about Cloudinary, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudinary is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Cloudinary from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Cloudinary tools
Cloudinary tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Cloudinary call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Cloudinary returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Cloudinary has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Cloudinary integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Cloudinary: link your Cloudinary account once in the browser and OpenClaw can call the Cloudinary API through 108 ready-made tools — no custom code or token handling.
How do I add Cloudinary to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Cloudinary skill from ClawHub, then you click Connect in the dashboard to authorize Cloudinary. OpenClaw calls the tools from the next message — no config files, and the Cloudinary key you paste is stored server-side instead of in your environment.
How long does it take to connect Cloudinary to OpenClaw?
About two minutes. Sign in, click Connect next to Cloudinary in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Cloudinary up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cloudinary working from chat.
OpenClaw installed the Cloudinary skill but can't call the tools
The ClawHub skill teaches OpenClaw about Cloudinary, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudinary is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
