Docker Hub integrationDocker Hub logo

Docker Hub integration for AI agents.

Docker Hub integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Docker Hub tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

What your agents can do

Real Docker Hub actions, managed and audited.

Your user connects Docker Hub once; your agent can then the world's largest container registry built for developers and open source contributors to find, use, and share their container images. Build, push and pull — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

  1. 1

    Your user grants Docker Hub access once (OAuth) — the token lands in the vault.

  2. 2

    Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.

  3. 3

    Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Docker Hub tools.

0 tools are generated from the published Docker Hub catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.

No tools match “”.

FAQ

Docker Hub integration, answered

How do AI agents use Docker Hub through Open Connector?
Your user connects Docker Hub once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Docker Hub tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Docker Hub MCP server?
Yes. Open Connector can serve Docker Hub as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Docker Hub actions with credentials injected server-side.
Where do Docker Hub credentials live?
In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Docker Hub — keep the keys.

Open source, self-hostable, with Docker Hub credentials that never leave your infrastructure. Run it from source today.