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


Uploadcare is a comprehensive file handling service that offers uploading, storage, processing, and delivery solutions for web and mobile applications.. Once connected, OpenClaw can read and act on Uploadcare from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Uploadcare 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 Uploadcare setup: install one ClawHub skill, connect Uploadcare in the browser, and OpenClaw can call real Uploadcare actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Uploadcare.
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 Uploadcare
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Uploadcare?"
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 Uploadcare in the ClawLink dashboard — paste your Uploadcare API key once.
Verify the connection by asking OpenClaw:
Use Uploadcare to check aws rekognition moderation status 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 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.
Uploadcare MCP for OpenClaw
Looking for a Uploadcare MCP server for OpenClaw? ClawLink connects Uploadcare to OpenClaw and exposes 34 Uploadcare tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Uploadcare integration works the same way.
What the OpenClaw Uploadcare integration can do
34 Uploadcare tools are ready for OpenClaw 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 OpenClaw
| 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 |
Try it: find the Uploadcare tool you need
Browse the 28 Uploadcare tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Uploadcare to check aws rekognition moderation status and walk me through the result in plain English.
Use Uploadcare to check remove bg status and walk me through the result in plain English.
Pull the relevant data from Uploadcare, summarize it in plain English, and point out anything that needs attention.
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 OpenClaw. 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 OpenClaw 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 comparison.
Troubleshooting
OpenClaw installed the Uploadcare skill but can't call the tools
The ClawHub skill teaches OpenClaw about Uploadcare, but the calls run through the ClawLink plugin and your connected account. Make sure Uploadcare 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 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.
FAQ
Is there a OpenClaw Uploadcare integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Uploadcare: link your Uploadcare account once in the browser and OpenClaw can call the Uploadcare API through 34 ready-made tools — no custom code or token handling.
How do I add Uploadcare to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Uploadcare skill from ClawHub, then you click Connect in the dashboard to authorize Uploadcare. OpenClaw calls the tools 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 OpenClaw?
About two minutes. Sign in, click Connect next to Uploadcare in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Uploadcare working from chat.
OpenClaw installed the Uploadcare skill but can't call the tools
The ClawHub skill teaches OpenClaw about Uploadcare, but the calls run through the ClawLink plugin and your connected account. Make sure Uploadcare 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.