# How to connect ImageKit to OpenClaw (paste one key, 26 tools) > Connect ImageKit to OpenClaw with ClawLink: paste your ImageKit key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/imagekit-io The usual route to ImageKit 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 ImageKit setup: install one ClawHub skill, connect ImageKit in the browser, and OpenClaw can call real ImageKit 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 ImageKit. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect ImageKit** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 imagekit-io # connect ImageKit (browser OAuth) npx -y @useclawlink/cli actions imagekit-io # list available actions npx -y @useclawlink/cli run imagekit-io --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 ImageKit in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your ImageKit API key once. Verify the connection by asking OpenClaw: > Use ImageKit to bulk job 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once ImageKit is connected in the dashboard, that agent calls the same 26 ImageKit 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). ## ImageKit MCP for OpenClaw Looking for a ImageKit MCP server for OpenClaw? ClawLink connects ImageKit to OpenClaw and exposes 26 ImageKit 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 Hermes instead? The [Hermes ImageKit integration](https://claw-link.dev/hermes/imagekit-io) works the same way. ## What the OpenClaw ImageKit integration can do 26 ImageKit tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 26. ### 19 of 26 ImageKit tools for OpenClaw | Tool | What it does | |---|---| | **Bulk job status** `imagekit_io_bulk_job_status` | Retrieve the status of a bulk folder operation | | **Get authentication parameters** `imagekit_io_get_authentication_parameters` | Generate authentication parameters for client-side file uploads | | **Get file details** `imagekit_io_get_file_details` | Retrieve details of a specific file | | **Get file metadata** `imagekit_io_get_file_metadata` | Retrieve metadata of an uploaded file | | **Get file version details** `imagekit_io_get_file_version_details` | Retrieve details of a specific file version | | **Get usage** `imagekit_io_get_usage` | Retrieve ImageKit account usage metrics for a specified date range | | **List and search assets** `imagekit_io_list_and_search_assets` | List and search media assets (files, folders, file-versions) in your ImageKit media library | | **List custom metadata fields** `imagekit_io_list_custom_metadata_fields` | List all custom metadata fields defined in the ImageKit Media Library | | **List file versions** `imagekit_io_list_file_versions` | Retrieves all versions of a specific file in ImageKit | | **Bulk move files** `imagekit_io_bulk_move_files` | Move multiple files in bulk | | **Bulk remove tags** `imagekit_io_bulk_remove_tags` | Remove tags from multiple files in bulk | | **Copy folder** `imagekit_io_copy_folder` | Initiate an asynchronous bulk copy of a folder and all its contents to a new location | | **Create custom metadata field** `imagekit_io_create_custom_metadata_field` | Create a new custom metadata field in ImageKit DAM | | **Create folder** `imagekit_io_create_folder` | Creates a new folder in ImageKit.io media library | | **Move folder** `imagekit_io_move_folder` | Move a folder from one location to another in your ImageKit media library | | **Rename file** `imagekit_io_rename_file` | Renames an existing file in the ImageKit media library | | **Restore file version** `imagekit_io_restore_file_version` | Restores a non-current file version to become the current version in ImageKit | | **Update custom metadata field** `imagekit_io_update_custom_metadata_field` | Updates an existing custom metadata field's label or schema constraints in ImageKit DAM | | **Update file details** `imagekit_io_update_file_details` | Update file details in ImageKit media library | ## Example prompts **Bulk Job Status** > Use ImageKit to bulk job status and walk me through the result in plain English. **Get Authentication Parameters** > Pull the relevant data from ImageKit, summarize it in plain English, and point out anything that needs attention. **Get File Details** > Pull the relevant data from ImageKit, summarize it in plain English, and point out anything that needs attention. **Get File Metadata** > Pull the relevant data from ImageKit, 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 ImageKit working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the ImageKit API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected ImageKit 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 ImageKit. | 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 ImageKit actions to the runtime in a format your agent can reliably use. | 26 tools for ImageKit are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ImageKit 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 ImageKit in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the ImageKit 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. ### OpenClaw installed the ImageKit skill but can't call the tools The ClawHub skill teaches OpenClaw about ImageKit, but the calls run through the ClawLink plugin and your connected account. Make sure ImageKit 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 ImageKit 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 ImageKit tools ImageKit 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 ImageKit 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. ### ImageKit 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 ImageKit has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw ImageKit integration? Yes. ClawLink is the fastest way to connect OpenClaw to ImageKit: link your ImageKit account once in the browser and OpenClaw can call the ImageKit API through 26 ready-made tools — no custom code or token handling. ### How do I add ImageKit to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink ImageKit skill from ClawHub, then you click Connect in the dashboard to authorize ImageKit. OpenClaw calls the tools from the next message — no config files, and the ImageKit key you paste is stored server-side instead of in your environment. ### How long does it take to connect ImageKit to OpenClaw? About two minutes. Sign in, click Connect next to ImageKit in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring ImageKit 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 ImageKit working from chat. ### OpenClaw installed the ImageKit skill but can't call the tools The ClawHub skill teaches OpenClaw about ImageKit, but the calls run through the ClawLink plugin and your connected account. Make sure ImageKit 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. ## Related - [OpenClaw Box integration](https://claw-link.dev/openclaw/box) — Store, share, and manage files and folders - [Supabase](https://claw-link.dev/openclaw/supabase) — Query and manage Postgres databases - [Dropbox tools](https://claw-link.dev/openclaw/dropbox) — Store, sync, and share files