# How to connect Cloudinary to Hermes Agent (paste one key, 108 tools) > Connect Cloudinary to Hermes with ClawLink: paste your Cloudinary key once and 108 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/cloudinary Most guides for giving Hermes Agent Cloudinary access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Cloudinary setup: pair once in the browser and your always-on Hermes agent can act on Cloudinary for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Hermes to Cloudinary. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Cloudinary** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect cloudinary # connect Cloudinary (browser OAuth) npx -y @useclawlink/cli actions cloudinary # list available actions npx -y @useclawlink/cli run cloudinary --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Cloudinary in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cloudinary API key once. Verify the connection by asking Hermes: > Use Cloudinary to activate live stream and walk me through the result in plain English. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Cloudinary MCP for Hermes Looking for a Cloudinary MCP server for Hermes Agent? ClawLink connects Cloudinary to Hermes Agent and exposes 108 Cloudinary tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Cloudinary integration](https://claw-link.dev/openclaw/cloudinary) works the same way. ## What the Hermes Agent Cloudinary integration can do 108 Cloudinary tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Activate Live Stream** > Use Cloudinary to activate live stream and walk me through the result in plain English. **Create Asset Relations By Asset Id** > Create it in Cloudinary for me, then confirm the important fields before you finish. **Create Asset Relations By Public Id** > Create it in Cloudinary for me, then confirm the important fields before you finish. **Create Folder** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Cloudinary Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Cloudinary integration? Yes. ClawLink is the fastest way to connect Hermes to Cloudinary: link your Cloudinary account once in the browser and Hermes Agent can call the Cloudinary API through 108 ready-made tools — no custom code or token handling. ### How do I connect Cloudinary to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Cloudinary in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Cloudinary in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Cloudinary working from chat. ### Hermes paired but still can't use Cloudinary Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Penpot](https://claw-link.dev/hermes/penpot) — Open-source design and prototyping platform for collaborative design workflows. - [Hermes Canva integration](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates - [Figma](https://claw-link.dev/hermes/figma) — Design files, prototypes, comments, and developer resources