# How to connect Uploadcare to Hermes Agent (paste one key, 34 tools)

> Connect Uploadcare to Hermes with ClawLink: paste your Uploadcare key once and 34 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/uploadcare

Most guides for giving Hermes Agent Uploadcare 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 Uploadcare setup: pair once in the browser and your always-on Hermes agent can act on Uploadcare for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to Uploadcare.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Uploadcare** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**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.

**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 uploadcare  # connect Uploadcare (browser OAuth)
npx -y @useclawlink/cli actions uploadcare  # list available actions
npx -y @useclawlink/cli run uploadcare <action> --input '<json>'  # 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 Uploadcare in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Uploadcare API key once.

Verify the connection by asking Hermes:

> Use Uploadcare to check aws rekognition moderation status 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 Uploadcare is connected in the dashboard, that agent calls the same 34 Uploadcare 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).

## Uploadcare MCP for Hermes

Looking for a Uploadcare MCP server for Hermes Agent? ClawLink connects Uploadcare to Hermes Agent and exposes 34 Uploadcare 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 Uploadcare integration](https://claw-link.dev/openclaw/uploadcare) works the same way.

## What the Hermes Agent Uploadcare integration can do

34 Uploadcare tools are ready for Hermes Agent once the account is connected. The 28 below are the ones people reach for most; your agent can call all 34.

### 28 of 34 Uploadcare tools for Hermes

| Tool | What it does |
|---|---|
| **Check aws rekognition moderation status** `uploadcare_check_aws_rekognition_moderation_status` | Check the execution status of AWS Rekognition Moderation labels detection |
| **Check remove bg status** `uploadcare_check_remove_bg_status` | Check Remove.bg execution status and get the UUID of the file with removed background |
| **Get aws rekognition execution status** `uploadcare_get_aws_rekognition_execution_status` | Check AWS Rekognition execution status for label detection |
| **Get clamav scan status** `uploadcare_get_clamav_scan_status` | Check the execution status of a ClamAV virus scan |
| **Get file group info upload** `uploadcare_get_file_group_info_upload` | Get information about a file group from the Upload API |
| **Get file info** `uploadcare_get_file_info` | Get information about a specific file |
| **Get file metadata** `uploadcare_get_file_metadata` | Retrieve all metadata key-value pairs associated with an Uploadcare file |
| **Get file metadata key** `uploadcare_get_file_metadata_key` | Get the value of a specific metadata key for an Uploadcare file |
| **Get group info** `uploadcare_get_group_info` | Get information about a specific file group |
| **Get project info** `uploadcare_get_project_info` | Get information about the current Uploadcare project |
| **Get uploaded file info** `uploadcare_get_uploaded_file_info` | Get information about an uploaded file using Uploadcare's Upload API |
| **Get URL upload status** `uploadcare_get_url_upload_status` | Check the status of a URL upload task |
| **Image mirror** `uploadcare_image_mirror` | Mirror an image horizontally via Uploadcare CDN |
| **List files** `uploadcare_list_files` | List files in an Uploadcare project with pagination and optional filtering |
| **List groups** `uploadcare_list_groups` | List groups in the project |
| **List webhooks** `uploadcare_list_webhooks` | Retrieves all webhook subscriptions for the authenticated Uploadcare project |
| **Rotate image** `uploadcare_rotate_image` | Rotate an image by specified degrees counterclockwise |
| **Copy file local** `uploadcare_copy_file_local` | Copy a file to local storage within the same Uploadcare project |
| **Create file group upload** `uploadcare_create_file_group_upload` | Create a file group from already uploaded files using Uploadcare's Upload API |
| **Create webhook** `uploadcare_create_webhook` | Create a new webhook subscription to receive notifications when file events occur |
| **Execute clamav scan** `uploadcare_execute_clamav_scan` | Execute ClamAV virus scan on an uploaded file |
| **Start multipart upload** `uploadcare_start_multipart_upload` | Start a multipart upload session for files larger than 100MB |
| **Store batch files** `uploadcare_store_batch_files` | Store multiple files in one request |
| **Store file** `uploadcare_store_file` | Mark an Uploadcare file as permanently stored |
| **Store single file** `uploadcare_store_single_file` | Store a single file by UUID permanently |
| **Update file metadata key** `uploadcare_update_file_metadata_key` | Update or set the value of a specific metadata key for a file |
| **Update webhook** `uploadcare_update_webhook` | Update an existing webhook subscription by its ID |
| **Upload from URL** `uploadcare_upload_from_url` | Upload a file from a publicly available URL to Uploadcare |

## Example prompts

**Check Aws Rekognition Moderation Status**

> Use Uploadcare to check aws rekognition moderation status and walk me through the result in plain English.

**Check Remove Bg Status**

> Use Uploadcare to check remove bg status and walk me through the result in plain English.

**Get Aws Rekognition Execution Status**

> Pull the relevant data from Uploadcare, summarize it in plain English, and point out anything that needs attention.

**Get Clamav Scan Status**

> Pull the relevant data from Uploadcare, summarize it in plain English, and point out anything that needs attention.

## 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 Uploadcare working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Uploadcare API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Uploadcare 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 Uploadcare. | 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 Uploadcare actions to the runtime in a format your agent can reliably use. | 34 tools for Uploadcare are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Uploadcare 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 Uploadcare in the browser, and the 34 tools above work from chat. There is no SDK and no config file, and the Uploadcare 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 Uploadcare
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 Uploadcare 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 Uploadcare tools
Uploadcare 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 Uploadcare 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.

### Uploadcare 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 Uploadcare 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 Uploadcare integration?
Yes. ClawLink is the fastest way to connect Hermes to Uploadcare: link your Uploadcare account once in the browser and Hermes Agent can call the Uploadcare API through 34 ready-made tools — no custom code or token handling.

### How do I connect Uploadcare 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 Uploadcare in the dashboard and Hermes can use it from the next message — no config files, and the Uploadcare key you paste is stored server-side instead of in your environment.

### How long does it take to connect Uploadcare to Hermes Agent?
About two minutes. Sign in, click Connect next to Uploadcare in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Uploadcare 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 Uploadcare working from chat.

### Hermes paired but still can't use Uploadcare
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

- [Box tools](https://claw-link.dev/hermes/box) — Store, share, and manage files and folders
- [Hermes Supabase integration](https://claw-link.dev/hermes/supabase) — Query and manage Postgres databases
- [Hermes Dropbox integration](https://claw-link.dev/hermes/dropbox) — Store, sync, and share files