What can you do with the Docker Hub integration?

LiveContext exposes 21 operations on Docker Hub, covering repository, tag, webhook and organization. Common uses include webhook administration, removing old versions and managing team structure.

LiveContext

All integrations

Docker Hub integration

Docker Hub container registry API for managing repositories, images, tags, and organizations. Search for images, manage automated builds, and control access to container repositories.

21 toolsTokenAPI docs

Connect Docker Hub How integrations work

Common Docker Hub use cases

webhook administration
removing old versions
managing team structure
monitoring build status
displaying user profiles
finding container images
removing unused webhooks
verifying authentication
verifying image versions
browsing user repositories

What you can do with Docker Hub

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Repository, 6 operations

POSTcreate_repository
Creates a new Docker Hub repository in the specified namespace. Allows setting the name, description, and visibility (public or private).
DELETEdelete_repository
Permanently deletes a Docker Hub repository and all its tags and images. This action cannot be undone.
GETget_repository
Retrieves detailed metadata for a specific Docker Hub repository including description, star count, pull count, and last update time.
GETlist_repositories
Lists all repositories within a Docker Hub namespace. Returns repository names, descriptions, star counts, pull counts, and last update timestamps. Supports pagination.
GETsearch_repositories
Searches Docker Hub repositories by keyword. Returns matching repositories with pull counts, star counts, and official/automated status indicators.
PATCHupdate_repository
Updates metadata for an existing Docker Hub repository including description, full description, and visibility settings.

Tag, 3 operations

DELETEdelete_tag
Deletes a specific tag from a Docker Hub repository. The underlying image layers may be retained if referenced by other tags.
GETget_tag
Retrieves detailed information about a specific tag including its digest, size, architecture variants, and last update time.
GETlist_tags
Lists all tags for a Docker Hub repository with image size, digest, architecture, and last update information. Supports pagination and filtering.

Webhook, 3 operations

POSTcreate_webhook
Creates a new webhook for a Docker Hub repository that fires when images are pushed. Supports multiple target URLs per webhook.
DELETEdelete_webhook
Deletes a specific webhook from a Docker Hub repository. Removes the webhook and all its associated hook URLs.
GETlist_webhooks
Lists all webhooks configured for a Docker Hub repository. Returns webhook names, URLs, and their current status.

Organization, 2 operations

GETget_org
Retrieves detailed information about a Docker Hub organization including its name, member count, team count, and subscription details.
GETlist_user_orgs
Lists all Docker Hub organizations the authenticated user is a member of. Returns organization names, IDs, and membership details.

User, 2 operations

GETget_authenticated_user
Retrieves the currently authenticated user's account information including username, email, and account details.
GETget_user
Retrieves public profile information for a Docker Hub user including their ID, username, full name, location, company, and registration date.

Auth, 1 operation

POSTlogin
Authenticates with Docker Hub and returns a JWT token. The token should be used as a Bearer token in the Authorization header for all subsequent API requests.

Build, 1 operation

GETget_build_history
Retrieves the automated build history for a Docker Hub repository including build status, trigger source, and timestamps.

Dockerfile, 1 operation

GETget_dockerfile
Retrieves the Dockerfile content for a Docker Hub repository with automated builds. Returns the raw Dockerfile text used to build the image.

Member, 1 operation

GETlist_org_members
Lists all members of a Docker Hub organization with their usernames, roles, and join dates. Requires organization admin access.

Team, 1 operation

GETlist_org_teams
Lists all teams within a Docker Hub organization including team names, descriptions, and member counts. Requires organization membership.

Use Docker Hub from Claude Code, Cursor or Codex

Connect Docker Hub in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Docker Hub operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Docker Hub

Create your workspace
Sign up free. Nothing to install.
Connect Docker Hub once
Add your Docker Hub connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Docker Hub integration FAQ

What can you do with the Docker Hub integration?: LiveContext exposes 21 operations on Docker Hub, covering repository, tag, webhook and organization. Common uses include webhook administration, removing old versions and managing team structure.