developer-toolsoauth2

Docker Hub

Container images, builds.

Verdict

Docker Hub integration lets your team search container images, check tags, and pull repository metadata without leaving Switchy. An @mention typically surfaces image versions, download counts, and last-updated timestamps — useful when deciding which base image to use or auditing what's deployed. Engineers and DevOps get the most value during sprint planning or incident response. Note that this MCP surfaces read-only data; you can't push images or manage repositories from chat.

Common use cases

Compare base image versions before a build
Audit which tags exist in production repos
Check download counts for internal images
Find the latest digest for a container
Surface deprecated images during planning

Integration

Vendor: Docker Hub
Category: developer-tools
Auth: OAUTH2
Composio slug: docker

Tools

Per-tool listings haven't synced yet for Docker Hub. The connection itself works - your Space can already @-mention it. Tool descriptions will fill in on the next Composio ingest.

Setup

Setup guide

11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Find Docker Hub in the developer tools section and click Connect. 3. You'll redirect to Docker Hub's OAuth consent screen — sign in with your Docker ID. 4. Grant read access to your public and private repositories (the MCP needs this scope to fetch metadata). 5. Docker Hub redirects you back to Switchy with a success message. 6. Open any Space and type '@Docker Hub list my repositories' to confirm the connection works. 7. If you see a list of repos with star counts and pull stats, you're ready to go.

What teammates see: by default, memories from Docker Hub are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List My Repositories

@Docker Hub show me all repositories in my account, sorted by most recently updated

Open in a Space →

Find Image Tags

@Docker Hub what tags are available for the nginx image, and when was each one last updated

Open in a Space →

Check Pull Stats

@Docker Hub how many pulls does our company/api-gateway image have, and what's the star count

Open in a Space →

Compare Base Images

@Docker Hub compare the python:3.11-slim and python:3.11-alpine images — show me size and last updated

Open in a Space →

Audit Deployed Digests

@Docker Hub what's the current digest for the redis:7.2 tag, and when was it published

Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@dockerhub show me the latest tags and pull counts for the nginx image, sorted by most recent

Output

The nginx repository shows 847 tags. Most recent: nginx:1.25.3 (published 2 days ago, 2.1M pulls), nginx:1.25.3-alpine (published 2 days ago, 890K pulls), nginx:mainline (published 3 days ago, 1.4M pulls). The 'latest' tag points to 1.25.3 and has accumulated 156M total pulls. All tags are official images maintained by the Docker Community.

Notes

This example demonstrates read access to public repository metadata. OAuth2 scope determines whether you can query private repositories in your organization. Pull counts update hourly but may lag during high-traffic periods. Rate limits apply: 100 requests per 6 hours for authenticated users.

Prompt

@dockerhub create a new repository called 'api-gateway' in our team namespace, set it to private, and add the description 'Internal routing service for microservices'

Output

Created private repository 'yourteam/api-gateway' in the yourteam namespace. Description set to 'Internal routing service for microservices'. Repository URL: hub.docker.com/r/yourteam/api-gateway. No tags pushed yet. Default visibility is private as requested. Team members with write access can now push images using 'docker push yourteam/api-gateway:tag'.

Notes

This example requires OAuth2 write scope and organization admin permissions. The MCP cannot push image layers — it only manages repository metadata. You'll still use docker CLI to push actual images. Repository creation counts against your organization's private repository quota on Docker Hub's paid plans.

Prompt

@dockerhub list all repositories in our organization that haven't been updated in the last 90 days and summarize which ones have zero pulls

Output

Found 12 repositories with no updates in 90+ days. Zero pulls: 'legacy-worker' (created 14 months ago, never pulled), 'test-harness-v2' (created 8 months ago, never pulled), 'prototype-api' (created 11 months ago, never pulled). Low activity (under 50 pulls): 'backup-service' (last updated 120 days ago, 12 pulls), 'cron-scheduler' (last updated 95 days ago, 31 pulls). These may be candidates for archival or deletion to reduce storage costs.

Notes

This example pairs Docker Hub's repository listing with AI reasoning to identify unused assets. Useful for cleanup audits in organizations with many experimental images. The MCP fetches metadata; the AI interprets patterns. Results depend on your OAuth2 scope covering all namespaces you want to audit.

Use-case deep-dives

Container image audit for compliance

When Docker Hub MCP helps security teams track image provenance

A 6-person platform team at a fintech startup needs to audit which container images are running in production and trace them back to their Docker Hub origins. The Docker Hub MCP lets them query image metadata, tags, and pull counts without leaving their Switchy workspace. OAuth2 auth means the team can connect once and share read access across the group. This works well when you're auditing fewer than 50 repositories and need quick answers during incident reviews. If you're managing hundreds of images or need real-time vulnerability scanning, you'll want a dedicated registry tool instead. For teams doing quarterly compliance checks or onboarding new engineers who need to understand the image landscape, this MCP closes the loop without context-switching to the Docker Hub web UI.

Onboarding documentation for containerized apps

How Docker Hub MCP speeds up new developer ramp-up

A 3-person backend team onboards a junior engineer who needs to understand which Docker images the codebase depends on and why. The Docker Hub MCP pulls README content, tag history, and download stats directly into Switchy, so the team can annotate images with context and link them to runbooks. OAuth2 keeps the setup friction low—one senior engineer connects the account and the whole team inherits access. This scenario wins when your stack uses 10-20 public or private images and you want a single source of truth for "what does this image do and when do we update it." If your images live in a private registry like ECR or GCR, this MCP won't help. For small teams running Docker Compose or Kubernetes locally, it turns image discovery into a shared learning artifact instead of a scavenger hunt.

Release coordination across microservices

When Docker Hub MCP clarifies which image versions shipped

A 5-person product team ships 8 microservices, each with its own Docker image, and needs to confirm which versions deployed to staging before promoting to production. The Docker Hub MCP lets them check tag timestamps, pull counts, and layer sizes without opening a browser. OAuth2 means the PM and QA lead can query image metadata alongside the engineers. This works when your release cadence is weekly or slower and you're coordinating fewer than a dozen services. If you're deploying multiple times a day or managing 50+ images, you need a CI/CD dashboard with richer deployment history. For teams that treat Docker Hub as the canonical registry and want a quick "what's live right now" check during standups, this MCP keeps everyone on the same page without Slack back-and-forth.

Frequently asked

What does the Docker Hub MCP do in Switchy?

It connects your Docker Hub account so AI agents can query repository metadata, check image tags, and read manifest details without leaving the chat. You won't push or pull images through Switchy — this is for discovery and inspection workflows where the AI needs to see what's published in your registries.

Does Docker Hub MCP need admin access to my organization?

No. OAuth2 scopes typically request read access to repositories you already have permission to view. If your Docker Hub org uses team-based access control, the MCP will inherit whatever visibility your personal account has. You don't need to be an org owner to connect it.

Can it pull images or trigger builds?

No. This MCP is read-only by design — it queries registry data but doesn't mutate anything. If you need to automate builds or deployments, use Docker Hub webhooks or the Docker CLI directly. The MCP exists to help agents answer questions like "what's the latest tag for this image" during planning conversations.

Why use this instead of just checking Docker Hub in a browser?

You save context-switching when the AI can look up image details mid-conversation. If you're debugging a deployment or comparing versions across repos, the agent fetches that data inline instead of you tabbing out, copying SHA hashes, and pasting them back. It's faster for repetitive lookups.

Who on the team should connect Docker Hub?

Whoever owns the Docker Hub account your team uses for shared images. If you have separate personal and org accounts, connect the org one so agents can see private repositories. Each Switchy user connects their own OAuth session — there's no shared credential to manage.