How to connect Docker Hub to Hermes Agent
Connect Docker Hub to Hermes with ClawLink: paste your Docker Hub key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine.
Docker HubAPI KEYMCPDocker Hub is a service provided by Docker for finding and sharing container images with your team.. Once connected, Hermes Agent can read and act on Docker Hub from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Docker Hub 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 Docker Hub setup: pair once in the browser and your always-on Hermes agent can act on Docker Hub 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 Docker Hub.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Docker Hub
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Docker Hub?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Docker Hub in the ClawLink dashboard — paste your Docker Hub API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention.
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:
npx -y @useclawlink/cli loginlogin 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.
Docker Hub MCP for Hermes
Looking for a Docker Hub MCP server for Hermes Agent? ClawLink connects Docker Hub to Hermes Agent and exposes 24 Docker Hub tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Docker Hub integration works the same way.
What the Hermes Agent Docker Hub integration can do
24 Docker Hub tools are ready for Hermes Agent 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 Hermes
| 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) |
Try it: find the Docker Hub tool you need
Browse the 17 Docker Hub tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Docker Hub, summarize it in plain English, and point out anything that needs attention.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Docker Hub
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 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.
FAQ
Is there a Hermes Agent Docker Hub integration?
Yes. ClawLink is the fastest way to connect Hermes to Docker Hub: link your Docker Hub account once in the browser and Hermes Agent can call the Docker Hub API through 24 ready-made tools — no custom code or token handling.
How do I connect Docker Hub 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 Docker Hub in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Docker Hub in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Docker Hub working from chat.
Hermes paired but still can't use Docker Hub
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
GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty tools
Manage incidents, on-call schedules, and services
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.