# How to connect Docker Hub to OpenClaw (paste one key, 24 tools) > Connect Docker Hub to OpenClaw with ClawLink: paste your Docker Hub key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/docker-hub The usual route to Docker Hub 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 Docker Hub setup: install one ClawHub skill, connect Docker Hub in the browser, and OpenClaw can call real Docker Hub 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 Docker Hub. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Docker Hub** — 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 docker-hub # connect Docker Hub (browser OAuth) npx -y @useclawlink/cli actions docker-hub # list available actions npx -y @useclawlink/cli run docker-hub --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 Docker Hub in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Docker Hub API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention. ### 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 Docker Hub is connected in the dashboard, that agent calls the same 24 Docker Hub 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). ## Docker Hub MCP for OpenClaw Looking for a Docker Hub MCP server for OpenClaw? ClawLink connects Docker Hub to OpenClaw and exposes 24 Docker Hub 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 Docker Hub integration](https://claw-link.dev/hermes/docker-hub) works the same way. ## What the OpenClaw Docker Hub integration can do 24 Docker Hub tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 24. ### 17 of 24 Docker Hub tools for OpenClaw | Tool | What it does | |---|---| | **Get image** `docker_hub_get_image` | Retrieve details about a specific platform-specific image variant by its digest | | **Get repository** `docker_hub_get_repository` | Retrieves detailed information about a specific Docker Hub repository | | **Get tag** `docker_hub_get_tag` | Retrieve details of a specific Docker Hub repository tag | | **Get team** `docker_hub_get_team` | Retrieve details of a specific team (group) within a Docker Hub organization | | **Get webhook** `docker_hub_get_webhook` | Retrieves details of a specific Docker Hub webhook by its ID | | **List org access tokens** `docker_hub_list_org_access_tokens` | List all organization access tokens for a Docker Hub organization | | **List org members** `docker_hub_list_org_members` | Lists members of a Docker Hub organization with their roles and details | | **List organizations** `docker_hub_list_organizations` | List Docker Hub organizations that the authenticated user belongs to | | **List repositories** `docker_hub_list_repositories` | List repositories under a namespace | | **List team members** `docker_hub_list_team_members` | List members of a Docker Hub team (group) within an organization | | **List teams** `docker_hub_list_teams` | List all teams (groups) within a Docker Hub organization | | **List webhooks** `docker_hub_list_webhooks` | Lists all webhooks configured for a Docker Hub repository | | **Add org member** `docker_hub_add_org_member` | Invite a user to join a Docker Hub organization | | **Create organization** `docker_hub_create_organization` | Create a new Docker Hub organization | | **Create repository** `docker_hub_create_repository` | Creates a new Docker Hub repository under the specified namespace | | **Create webhook** `docker_hub_create_webhook` | Create a webhook on a Docker Hub repository to receive notifications on image push events | | **Remove team member** `docker_hub_remove_team_member` | Remove a user from a Docker Hub organization team (group) | ## Example prompts **Get Image** > Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention. **Get Repository** > Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention. **Get Tag** > Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention. **Get Team** > Pull the relevant data from Docker Hub, 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 Docker Hub working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Docker Hub API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Docker Hub 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 Docker Hub. | 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 Docker Hub actions to the runtime in a format your agent can reliably use. | 24 tools for Docker Hub are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Docker Hub 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 Docker Hub in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the Docker Hub 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 Docker Hub skill but can't call the tools The ClawHub skill teaches OpenClaw about Docker Hub, but the calls run through the ClawLink plugin and your connected account. Make sure Docker Hub 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 Docker Hub 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 Docker Hub tools Docker Hub 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 Docker Hub 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. ### Docker Hub 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 Docker Hub has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Docker Hub integration? Yes. ClawLink is the fastest way to connect OpenClaw to Docker Hub: link your Docker Hub account once in the browser and OpenClaw can call the Docker Hub API through 24 ready-made tools — no custom code or token handling. ### How do I add Docker Hub to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Docker Hub skill from ClawHub, then you click Connect in the dashboard to authorize Docker Hub. OpenClaw calls the tools from the next message — no config files, and the Docker Hub key you paste is stored server-side instead of in your environment. ### How long does it take to connect Docker Hub to OpenClaw? About two minutes. Sign in, click Connect next to Docker Hub in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Docker Hub 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 Docker Hub working from chat. ### OpenClaw installed the Docker Hub skill but can't call the tools The ClawHub skill teaches OpenClaw about Docker Hub, but the calls run through the ClawLink plugin and your connected account. Make sure Docker Hub 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 - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.