Skip to main content
ClaudeWave

Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)

MCP ServersOfficial Registry0 stars0 forks● TypeScriptMITUpdated today
ClaudeWave Trust Score
95/100
✓ Verified
Passed
  • ✓Open-source license (MIT)
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Topics declared
  • ✓Documented (README)
Last scanned: 9/26/2026
Install in Claude Code / Claude Desktop
Method: NPX · @pipeworx/mcp-dockerhub
Claude Code CLI
claude mcp add mcp-dockerhub -- npx -y @pipeworx/mcp-dockerhub
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "mcp-dockerhub": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-dockerhub"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers overview

# mcp-dockerhub

Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1683+ live data sources.

## Tools

| Tool | Description |
|------|-------------|
| `search_images` | Search Docker Hub for container images by keyword. Returns repository name, description, pull count, star count, and official status. Use when finding images for deployment. |
| `get_image` | Get detailed metadata for a Docker Hub repository: description, pull count, stars, last updated date, and official status. Use before pulling an image to verify quality and currency. |
| `get_tags` | List available tags for a Docker image sorted by recency. Returns tag name, digest, size, and push date. Use to find and select specific versions to pull. |
| `get_tag_details` | Get full details for a SPECIFIC image tag, including every platform/architecture it supports (os/arch/variant), per-platform digests and sizes, the multi-arch manifest digest, and push date. PREFER for "does <image>:<tag> have an arm64 build", "what platforms does <image>:<tag> support", "the digest/size of <image>:<tag>", multi-arch verification. |

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "dockerhub": {
      "url": "https://gateway.pipeworx.io/dockerhub/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/dockerhub/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## No MCP client? Call it over HTTP

```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/dockerhub_search_images \
  -H 'Content-Type: application/json' \
  -d '{"query":"nginx"}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/dockerhub_search_images`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no
gateway round-trip:

```json
{
  "mcpServers": {
    "dockerhub": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-dockerhub"]
    }
  }
}
```

Or run it directly to confirm it starts:

```bash
npx -y @pipeworx/mcp-dockerhub
```

It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
for **only** this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Dockerhub data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT
dockerhubmcpmcp-servermodel-context-protocolpipeworx

What people ask about mcp-dockerhub

What is pipeworx-io/mcp-dockerhub?

+

pipeworx-io/mcp-dockerhub is mcp servers for the Claude AI ecosystem. Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data) It has 0 GitHub stars and its last recorded update is dated 2026-09-25.

How do I install mcp-dockerhub?

+

You can install mcp-dockerhub by cloning the repository (https://github.com/pipeworx-io/mcp-dockerhub) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is pipeworx-io/mcp-dockerhub safe to use?

+

Our security agent has analyzed pipeworx-io/mcp-dockerhub and assigned a Trust Score of 95/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.

Who maintains pipeworx-io/mcp-dockerhub?

+

pipeworx-io/mcp-dockerhub is maintained by pipeworx-io. The last recorded GitHub activity is dated 2026-09-25, with 0 open issues.

Are there alternatives to mcp-dockerhub?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy mcp-dockerhub to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: pipeworx-io/mcp-dockerhub
[![Featured on ClaudeWave](https://claudewave.com/api/badge/pipeworx-io-mcp-dockerhub)](https://claudewave.com/repo/pipeworx-io-mcp-dockerhub)
<a href="https://claudewave.com/repo/pipeworx-io-mcp-dockerhub"><img src="https://claudewave.com/api/badge/pipeworx-io-mcp-dockerhub" alt="Featured on ClaudeWave: pipeworx-io/mcp-dockerhub" width="320" height="64" /></a>

More MCP Servers

mcp-dockerhub alternatives