Menu
Mattering Automations connector

The Docker Hub MCP that runs your repos, teams, and org

Connect a Docker ID and personal access token once, and repositories, tags, immutable tag rules, teams, invites, and audit logs become workflow steps that automations run on a schedule and AI assistants run on request.

38 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Docker Hub MCP connector does

The Docker Hub connector for Mattering Automations covers the Hub management API with 38 nodes: create, update, and delete repositories, sync README content, list and delete tags, govern immutable tag rules, search public images, and administer an organization end to end with members, teams, invites, settings, and audit log queries. It was built against Docker's published Hub API reference, and where a stable route predates the official spec, the node description says exactly where it comes from.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. Docker itself is invested in MCP: its MCP Catalog and Toolkit distribute containerized MCP servers through Docker Desktop, and Docker publishes a Hub MCP server focused on image discovery. This connector is a different layer, and the two compose.

Because Mattering is a work platform rather than middleware, Docker Hub work lands somewhere useful by default: a nightly audit log query can write into a database, a stale-tag report can become a review task with an approval step before anything is deleted, and the whole flow lives on one canvas next to your other tools.

One connection, three surfaces

  • Visual automations. Drag Docker Hub nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Docker Hub node, ready to drop on the canvas

38 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 20

Docker Hub: Get Current User

Get the authenticated Docker Hub account: Docker ID, full name, company, and join date. Takes no parameters, so it doubles as the credential health check: a bad username or token fails before this call is even made. Stable route used by Docker's own hub-tool CLI as its whoami.

Docker Hub: Get Organization

Get one Docker Hub organization's profile: org name, full name, company, location, and join date. Stable route used by Docker's own hub-tool CLI.

Docker Hub: Get Organization Access Token

Get one organization access token's metadata by id, including the resources it can reach. The secret value is NOT returned.

Docker Hub: Get Organization Settings

Get an organization's settings, currently the restricted images policy (whether members may only use org images, official images, and verified publisher images). Requires org owner permission.

Docker Hub: Get Personal Access Token

Get one personal access token's metadata by UUID: label, scopes, active state, and expiry. The secret token value is NOT returned.

Docker Hub: Get Repository

Get one repository's full details: description, README (full_description), star and pull counts, privacy, media types, and immutable-tag settings.

Docker Hub: Get Repository Tag

Get one tag's details: compressed size, last push and pull times, status, and its per-platform images with digests at data.images[].

Docker Hub: Get Team

Get one team (group) in an organization: id, name, description, and member count.

Docker Hub: List Audit Log Actions

List the audit log action names available for a namespace, grouped by area, for use as the action filter on Docker Hub: List Audit Log Events.

Docker Hub: List Audit Log Events

Query audit log events for a namespace (org or user): who did what and when, at data.logs[]. Filter by action (for example repo.tag.push), object name, actor, and a time window. Requires permission on the account being queried.

Docker Hub: List My Organizations

List the Docker Hub organizations the authenticated account belongs to, with each org's name, company, and profile details. Stable route used by Docker's own hub-tool CLI.

Docker Hub: List Organization Access Tokens

List an organization's access tokens (OATs): label, creator, active state, and expiry. Requires org owner permission and an org on a paid subscription. Secret values are not returned. Read only by design.

Docker Hub: List Organization Invites

List an organization's pending invites: invitee (Docker ID or email), inviter, target team, and creation time at data.data[]. Requires org owner permission.

Docker Hub: List Organization Members

List an organization's members with username, email, role (Owner, Member, or Invitee), team memberships, and guest status. Requires permission to view the org's members.

Docker Hub: List Personal Access Tokens

List the authenticated account's personal access tokens: label, scopes, active state, creation and last-used times, and expiry. The secret token values are NOT returned (the token field comes back empty). Read only by design: creating or revoking credentials stays in the Docker Hub UI.

Docker Hub: List Repositories

List the image repositories in a namespace (a user or organization) with name, description, star and pull counts, and privacy. Supports partial name filtering and ordering by name, last_updated, or pull_count.

Docker Hub: List Repository Tags

List a repository's tags with size, push/pull timestamps, active/inactive status, and the per-platform image list (architecture, OS, digest) embedded in each tag at data.results[].images[].

Docker Hub: List Team Members

List the members of a team (group) with username, full name, and email. Search filters by username, full name, or email.

Docker Hub: List Teams

List an organization's teams (groups) with name, description, and member count. Filter by a member's username or search by team name.

Docker Hub: Search Repositories

Search public Docker Hub repositories by keyword, returning repo name, short description, star and pull counts, and official-image flags. Same index the docker search command uses; verified live against hub.docker.com.

Action nodes 18

Docker Hub: Add Team Member

Add an existing organization member to a team (group). Reversible via Docker Hub: Remove Team Member. The user must already belong to the organization.

Docker Hub: Cancel Invite

Cancel a pending organization invite by id. Reversible by sending a fresh invite to the same person.

Docker Hub: Create Repository

Create a new image repository in a namespace, optionally with a short description, a README (full_description), and private visibility. Reversible via Docker Hub: Delete Repository. Free accounts have limited private repositories, so is_private may be rejected on a full plan.

Docker Hub: Create Team

Create a new team (group) in an organization. Reversible via Docker Hub: Delete Team. Requires org owner permission.

Docker Hub: Delete Repository

DESTRUCTIVE: permanently delete a repository including all of its tags, its pull and star history, and its description. There is no trash and no restore. Stable route used by Docker's own hub-tool CLI (repo rm). The PAT needs delete scope.

Docker Hub: Delete Repository Tag

DESTRUCTIVE: delete a tag from a repository. The tag reference is gone immediately; the underlying image manifest survives only while another tag still points at it. Fails if the repository has immutable tags enabled and the tag matches a protected rule. Stable route used by Docker's own hub-tool CLI (tag rm). The PAT needs delete scope.

Docker Hub: Delete Team

DESTRUCTIVE: delete a team (group) from an organization. Its members stay in the org but the team's repository permissions are gone and must be rebuilt by hand. Requires org owner permission.

Docker Hub: Grant Team Repository Access

Grant a team (group) access to a repository at read, write, or admin level. Reversible by granting a lower level or removing the team's access in the Hub UI.

Docker Hub: Invite Members

Invite one or more users to an organization by Docker ID or email, optionally into a specific team and role. Each invite consumes a seat when accepted. Reversible via Docker Hub: Cancel Invite. Set dry_run true to validate without sending anything.

Docker Hub: Remove Organization Member

DESTRUCTIVE: remove a member from an organization. They lose access to the org's repositories and teams immediately; getting them back requires a fresh invite they must accept. Requires org owner permission.

Docker Hub: Remove Team Member

Remove a user from a team (group). They stay in the organization; reversible via Docker Hub: Add Team Member.

Docker Hub: Resend Invite

Resend the email for a pending organization invite by id. Changes no membership state.

Docker Hub: Update Immutable Tag Settings

Enable or disable immutable tags on a repository and set the regex rules for which tags are protected from being overwritten or deleted. Reversible by calling again with immutable_tags false or different rules.

Docker Hub: Update Organization Member Role

Change an organization member's role to owner, editor, or member. Requires org owner permission. Reversible by setting the previous role back.

Docker Hub: Update Organization Settings

Update an organization's restricted images policy: whether members are limited to the org's own images, and whether Docker official images and verified publisher images stay allowed. Reversible by putting the previous values back. Requires org owner permission.

Docker Hub: Update Repository Description

Update a repository's short description and/or its README-style full description (the classic push-README-from-CI call). Only the fields you fill are changed. Stable route without a documented replacement yet; it is the same call the widely-used dockerhub-description GitHub Action makes. The PAT needs write scope on the repository.

Docker Hub: Update Team

Rename a team (group) or change its description. Only the fields you fill are changed. Requires org owner permission.

Docker Hub: Verify Immutable Tag Rule

Dry-run an immutable-tag regex against a repository's existing tags: returns the list of tags the rule would protect, without changing any settings. Use before Docker Hub: Update Immutable Tag Settings.

Connecting Docker Hub takes one credential

Sign in at hub.docker.com and open Account settings, then Personal access tokens. Free Docker Personal accounts can create tokens, with Read, Write, or Delete permission levels and a custom expiry.

1

In Docker Hub, generate a personal access token with the permission level your workflows need. The delete nodes require Delete; most read and write workflows do fine with less.

2

In Mattering Automations, open Connectors, choose Docker Hub, and create a credential with your Docker ID as the username and the token as the password.

3

On each run the connector exchanges that pair for a short-lived session token at Docker's documented token endpoint, because Docker Hub's API does not accept a personal access token directly. Docker's API reference documents the session token as expiring in 10 minutes, and the connector never stores it.

4

Test Connection runs Docker Hub: Get Current User and reports the account it authenticated as. All 38 Docker Hub nodes appear in the canvas palette.

Common uses for the Docker Hub MCP

READMEs that never drift

A docs change or a CI run calls Docker Hub: Update Repository Description to push the short description and the full README to the repository, the same call the popular GitHub Action for Hub descriptions makes.

Tag hygiene on a schedule

A weekly workflow runs Docker Hub: List Repository Tags across your namespace, flags tags that have not been pushed or pulled recently, and files a review task. Approved tags are removed with Docker Hub: Delete Repository Tag.

Onboarding in one flow

A new-hire workflow runs Docker Hub: Invite Members, then Docker Hub: Add Team Member and Docker Hub: Grant Team Repository Access once the invite is accepted, so registry access tracks your HR checklist instead of a memory.

Audit log monitoring

A nightly query with Docker Hub: List Audit Log Events writes who did what into a Mattering database and alerts on the actions you care about, like repository deletions or membership changes.

Immutable tag governance

Docker Hub: Verify Immutable Tag Rule dry-runs a rule against a repository's existing tags so you can see exactly which tags it would protect, then Docker Hub: Update Immutable Tag Settings applies it. Rollouts across many repositories become a loop instead of an afternoon.

An assistant that knows your images

Ask Matter, Claude, or ChatGPT which tags a repository has, what platforms an image covers, or what public images match a keyword via Docker Hub: Search Repositories, and get answers from the live API instead of a stale wiki page.

Example: Stale tags get flagged, approved, and removed

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a weekly schedule starts the workflow.

2

Docker Hub: List Repositories pulls every repository in your namespace.

3

Docker Hub: List Repository Tags runs for each repository, and a filter step keeps tags with no recent push or pull activity.

4

The stale list lands as a review task in Mattering Productivity, and on approval Docker Hub: Delete Repository Tag removes each one.

Docker Hub MCP questions, answered

Can an AI agent manage Docker Hub through this MCP?

Yes. Matter and any MCP-connected assistant, including Claude and ChatGPT, can create and update repositories, sync READMEs, list and delete tags, manage teams and invites, and query audit logs, using the same 38 nodes available on the automation canvas. The four destructive nodes (deleting repositories, deleting tags, removing org members, deleting teams) are flagged as destructive so you can gate them behind approval.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

How is this different from Docker's MCP Catalog and Toolkit?

Docker's MCP Catalog and Toolkit is a distribution platform: a curated library of containerized MCP servers you run through Docker Desktop and connect to clients like Claude Desktop. Docker also publishes a Docker Hub MCP server focused on image discovery plus repository and tag tools. Mattering's connector is a different layer: the same Hub management surface plus organization administration (members, teams, invites, settings, audit logs), running inside a persistent automation platform where scheduled workflows execute without anyone in a chat session and results land in tasks, databases, and messages. They solve different problems and compose fine.

What credential does the connector use, and why not just a token?

A Docker ID plus a personal access token, stored encrypted in Google Secret Manager. Docker Hub's API does not accept a personal access token directly as a bearer credential: Docker's API reference says every authentication type must go through its token endpoint to obtain a short-lived session token, which Docker documents as expiring in 10 minutes. The connector performs that exchange on each run, which is also why it works on accounts with two-factor authentication and in orgs that enforce single sign-on.

Do I need a paid Docker plan?

Not for most of it. A free Docker Personal account can create personal access tokens and covers the account, repository, tag, and search nodes. The organization surfaces need an organization, and per Docker's documentation, organization access tokens and audit logs require a Docker Team or Business subscription.

What are Docker Hub's API rate limits?

Docker enforces per-minute request limits on the Hub API and reports them through X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers, answering 429 with a Retry-After header when you exceed them. Docker does not publish the numeric per-minute quota. These API limits are separate from image pull limits, which apply to pulling images, not to this connector.

Can it manage webhooks or react to image pushes?

No. Docker documents Hub webhooks as configured in the repository UI, with no published management API, so no webhook nodes ship and there are no push-event triggers. Workflows that need to notice changes run on a schedule and query tags or audit log events instead. Pushing and pulling images is the registry API, a separate surface this connector does not cover.

What is not supported?

Creating or revoking access tokens (the token nodes are read only on purpose, since credential management belongs in the Docker Hub UI), webhook management, pushing or pulling images, and vulnerability scanning. Everything the 38 nodes cover is listed on this page; if a node is not in the list, the connector does not do it.

38 nodes waiting on the canvas

Put Docker Hub to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Docker Hub is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products