接入你的智能体
发布者自己的 URL。不是 PlugMCP 端点。
用我们的密钥与日志托管一份副本。
https://gateway.pipeworx.io/dockerhub/mcp上方的 Claude 按钮会打开 Claude，并填好名称和 URL。你仍需在那里确认。
claude mcp add --transport http io.github.pipeworx-io-dockerhub https://gateway.pipeworx.io/dockerhub/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-dockerhub": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/dockerhub/mcp" ] } }}claude_desktop_config.json
远程 URL 还是本机命令？ 两种安装方式的区别
来自发布者
Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)
Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"dockerhub": {
"url": "https://gateway.pipeworx.io/dockerhub/mcp"
}
}
}
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:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1878+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"dockerhub": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-dockerhub"]
}
}
}
Or run it directly to confirm it starts:
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.
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.
MIT
Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)
{ "mcpServers": { "io.github.pipeworx-io-dockerhub": { "url": "https://gateway.pipeworx.io/dockerhub/mcp", "headers": {} } }}工具
暂无工具列表。远程服务器在首次健康检查后会获得工具列表。
常见问题
在本页复制适用于 Cursor、Claude Desktop、Claude Code 或 VS Code 的 http 配置。它使用发布者的安装方式，而不是 PlugMCP 代理。
发布者列出了以下环境变量：PIPEWORX_API_KEY。
Dockerhub 通过 HTTP 访问。
上次检查时间：2026-11-10。 Docker Hub MCP — wraps the Docker Hub v2 API (free, no auth required for public data)