# Docker Hub MCP connector

Connect Docker Hub to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client can manage your Docker Hub organization's members, teams, invites, access tokens and audit logs as the person who signed in.

Source: https://elaichi.ai/connectors/dockerhub/

## Facts

| | |
| --- | --- |
| Application | Docker Hub |
| Category | Application Development |
| AI tools | 44 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Docker Hub is connected

- Who in the platform group holds an org access token?
- Resend the pending invites for the mobile group.
- Show me every Docker Hub audit log entry from last week.

## Connect Docker Hub in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Docker Hub.
2. Optionally set Share with, then press Connect.
3. Paste a Docker Hub API key. One person generates a token in Docker Hub and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Docker Hub tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Docker Hub MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Docker Hub MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Docker Hub MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Docker Hub MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Docker Hub MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Docker Hub to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Docker Hub tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Docker Hub through Elaichi

### Invite a new engineer to the right teams

Platform. Send the Docker Hub invite and add the person to the groups their squad uses, in one ask instead of a trip through the admin screens.

### Review who holds an organization access token

Security. List every Docker Hub organization access token, see what it is for, and update or delete the ones that should not exist anymore.

### Offboard a leaver from Docker Hub quickly

IT. Change their member role, pull them out of every group and remove any pending invite, with each step recorded against the admin who asked.

### Pull the audit log for the quarter

Compliance. Ask for the Docker Hub audit log actions over a date range and get a readable summary of who changed what in the organization.

### Tidy up group membership before a release

Engineering. Check which Docker Hub groups a contractor still belongs to, compare it with the current project list, and fix the stragglers.

### Export the member list for a seat count

Finance. Run a bulk export of Docker Hub organization members and get a count of active seats before the renewal conversation.

## Elaichi vs Zapier MCP vs Composio for Docker Hub

All three can connect Docker Hub to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Docker Hub tools | Allow or restrict single Docker Hub tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Docker Hub call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Docker Hub to Claude?

Connect Docker Hub in Elaichi by pasting a Docker Hub API key, which you create in your Docker Hub account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in as yourself and Docker Hub is ready to use.

### Does Docker Hub work with ChatGPT and Cursor as well as Claude?

Yes. Once Docker Hub is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Docker Hub once and every client picks it up.

### What can an AI agent actually do with my Docker Hub data?

With Docker Hub connected, an agent can list your organization's members and groups, send or resend invites, add or remove people from groups, create and manage organization access tokens, export the member list and read the audit log. Short, concrete asks work best, such as "add Priya to the mobile group" rather than a long paragraph. It is the everyday admin work of a Docker Hub organization, done by asking.

### Does connecting Docker Hub give the AI everything in my organization?

No. Every call to Docker Hub runs as the person who signed in, so an agent can only see and change what that person's Docker Hub role already allows. Elaichi can narrow that further with restrictions, and it never widens it. An owner and a member get different results from the same prompt.

### Can my team share one Docker Hub connection?

Yes. One admin connects Docker Hub in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each person still signs in to Elaichi as themselves, so the audit log names the individual who asked for a change in Docker Hub, not the shared connection.

### Can I stop an agent from deleting or changing things in Docker Hub?

Yes. Restrictions in Elaichi work per action, so you can allow reading Docker Hub members and groups while restricting deleting a group, removing a member or creating an organization access token. A restriction is set on a role or on one person. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Docker Hub connection when someone leaves?

Offboarding a person in Elaichi ends their access to the Docker Hub connection at once, across every client. A shared Docker Hub connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Docker Hub once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Docker Hub MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Docker Hub is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Docker Hub?

Yes. Both let Claude, ChatGPT or Cursor use Docker Hub. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Docker Hub call.

### How is Elaichi different from Composio for Docker Hub?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Docker Hub: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 44 Docker Hub tools

Every tool below is callable through https://api.elaichi.ai/mcp once Docker Hub is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Docker Hub audit log actions** (List). List audit log actions. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password or an organization access token. [GET /v2/auditlogs/{account}/actions]
- **List all Docker Hub audit logs** (List). List audit log events. Audit logs need a Docker Team or Business subscription. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password or an organization access token. [GET /v2/auditlogs/{account}]
- **Create a Docker Hub auth token** (Create). Create access token. Creates and returns a short-lived access token in JWT format for use as a bearer when calling Docker APIs. If successful, the access token returned should be used in the HTTP Authorization header like Authorization: Bearer {accesstoken}. If your organization has SSO enforced, you must use a personal access token (PAT) instead of a password.**_ the connector calls this automatically at connect time and every 5 minutes with the connected identifier and secret; you rarely need to call it yourself. [POST /v2/auth/token]
- **List all Docker Hub group members** (List). List members of a group. List the members (users) that are in a group. If user is owner of the org or has otherwise elevated permissions, they can search by email and the result will also contain emails. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/groups/{group_name}/members]
- **Create a Docker Hub group member** (Create). Add a member to a group. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [POST /v2/orgs/{org_name}/groups/{group_name}/members]
- **Delete a Docker Hub group member by ID** (Delete). Remove a user from a group. The id is the Docker username to remove. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [DELETE /v2/orgs/{org_name}/groups/{group_name}/members/{username}]
- **List all Docker Hub groups** (List). Get groups of an organization. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/groups]
- **Create a Docker Hub group** (Create). Create a new group. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [POST /v2/orgs/{org_name}/groups]
- **Get single Docker Hub group by ID** (Get). Get a group of an organization. The id is the group (team) name. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/groups/{group_name}]
- **Update a Docker Hub group by ID** (Update). Update the details for an organization group. The id is the current group (team) name; name is required and description is replaced. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [PUT /v2/orgs/{org_name}/groups/{group_name}]
- **Docker Hub groups partial update** (Update). Update some details for an organization group. Pass the current group (team) name as group_id. Only the fields sent are changed. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [PATCH /v2/orgs/{org_name}/groups/{group_name}]
- **Delete a Docker Hub group by ID** (Delete). Delete an organization group. The id is the group (team) name. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [DELETE /v2/orgs/{org_name}/groups/{group_name}]
- **List all Docker Hub invites** (List). List org invites. Return all pending invites for a given org, only team owners can call this endpoint This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/invites]
- **Create a Docker Hub invite** (Create). Bulk create invites. Create multiple invites by emails or DockerIDs. Only a team owner can create invites. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [POST /v2/invites/bulk]
- **Delete a Docker Hub invite by ID** (Delete). Cancel an invite. Mark the invite as cancelled so it doesn't show up on the list of pending invites This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. The id is the invite id (from invites.list). Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [DELETE /v2/invites/{id}]
- **Docker Hub invites resend** (Resend). Resend an invite. Resend a pending invite to the user, any org owner can resend an invite This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [PATCH /v2/invites/{id}/resend]
- **List all Docker Hub org access tokens** (List). List access tokens. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/access-tokens]
- **Create a Docker Hub org access token** (Create). Create access token. Create an access token for an organization. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [POST /v2/orgs/{org_name}/access-tokens]
- **Get single Docker Hub org access token by ID** (Get). Get access token. Get details of a specific access token for an organization. The id is the access token id. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/access-tokens/{access_token_id}]
- **Update a Docker Hub org access token by ID** (Update). Update access token. Update a specific access token for an organization. The id is the access token id. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [PATCH /v2/orgs/{org_name}/access-tokens/{access_token_id}]
- **Delete a Docker Hub org access token by ID** (Delete). Delete access token. Delete a specific access token for an organization. This action cannot be undone. The id is the access token id. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [DELETE /v2/orgs/{org_name}/access-tokens/{access_token_id}]
- **List all Docker Hub org members** (List). List org members. Returns a list of members for an organization. The following fields are only visible to orgs with insights enabled. - lastloggedinat - lastseenat - lastdesktopversion` To make visible, please see View Insights for organization users. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/members]
- **Docker Hub org members bulk export** (Export). Export org members CSV. Export members of an organization as a CSV This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. Returns the CSV file text. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/members/export]
- **Update a Docker Hub org member by ID** (Update). Update org member (role). Updates the role of a member in the organization. Only users in the "owners" group of the organization can use this endpoint. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. The id is the member's Docker username. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [PUT /v2/orgs/{org_name}/members/{username}]
- **Delete a Docker Hub org member by ID** (Delete). Remove member from org. Removes the member from the org, ie. all groups in the org, unless they're the last owner This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. The id is the member's Docker username. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [DELETE /v2/orgs/{org_name}/members/{username}]
- **Docker Hub org settings lookup** (Action). Get organization settings. Returns organization settings by name. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/orgs/{org_name}/settings]
- **Docker Hub org settings bulk update** (Update). Update organization settings. Updates an organization's settings. Some settings are only used when the organization is on a business subscription. Only users with administrative privileges for the organization (owner role) can modify these settings. The following settings are only used on a business subscription: - restrictedimages` Replaces the organization settings for org_name. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [PUT /v2/orgs/{org_name}/settings]
- **List all Docker Hub personal access tokens** (List). List personal access tokens. Returns a paginated list of personal access tokens. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/access-tokens]
- **Create a Docker Hub personal access token** (Create). Create personal access token. Creates and returns a personal access token. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [POST /v2/access-tokens]
- **Get single Docker Hub personal access token by ID** (Get). Get personal access token. Returns a personal access token by UUID. The id is the token UUID. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [GET /v2/access-tokens/{uuid}]
- **Update a Docker Hub personal access token by ID** (Update). Update personal access token. Updates a personal access token partially. You can either update the token's label or enable/disable it. The id is the token UUID. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [PATCH /v2/access-tokens/{uuid}]
- **Delete a Docker Hub personal access token by ID** (Delete). Delete personal access token. Deletes a personal access token permanently. This cannot be undone. The id is the token UUID. Docker rejects connections made with a personal access token here (403 "token issued from personal access token is not allowed"); the account must be connected with the Docker password. [DELETE /v2/access-tokens/{uuid}]
- **List all Docker Hub repositories** (List). List repositories in a namespace. Returns a list of repositories within the specified namespace (organization or user). Public repositories are accessible to everyone, while private repositories require appropriate authentication and permissions. OAT listing behavior: an OAT with the scope-repository-list scope sees all repositories including private ones. An OAT without that scope only sees public repositories. This filtering is silent: the response is a normal 200 with no indication that private repositories were withheld. [GET /v2/namespaces/{namespace}/repositories]
- **Create a Docker Hub repository** (Create). Create a new repository. Creates a new repository within the specified namespace. The repository will be created with the provided metadata including name, description, and privacy settings. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. [POST /v2/namespaces/{namespace}/repositories]
- **Get single Docker Hub repository by ID** (Get). Get repository in a namespace. Returns a repository within the specified namespace (organization or user). Public repositories are accessible to everyone, while private repositories require appropriate authentication and permissions. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. The id is the repository name (without the namespace). [GET /v2/namespaces/{namespace}/repositories/{repository}]
- **Create a Docker Hub repository group** (Create). Assign a group (Team) to a repository for access. Assigns an organization group (team) to a repository with a specified permission level. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. [POST /v2/repositories/{namespace}/{repository}/groups]
- **Docker Hub repository immutable tags bulk update** (Update). Update repository immutable tags. Updates the immutable tags configuration for this repository. Only users with administrative privileges for the repository can modify these settings. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. Replaces the immutable-tag settings of the repository. [PATCH /v2/namespaces/{namespace}/repositories/{repository}/immutabletags]
- **Docker Hub repository immutable tags verify** (Verify). Verify repository immutable tags. Validates the immutable tags regex passed in the request body and returns a list of tags matching it in this repository. Only users with administrative privileges for the repository can call this endpoint. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. [POST /v2/namespaces/{namespace}/repositories/{repository}/immutabletags/verify]
- **List all Docker Hub repository tags** (List). List repository tags. Returns the list of tags for the specified repository. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. [GET /v2/namespaces/{namespace}/repositories/{repository}/tags]
- **Get single Docker Hub repository tag by ID** (Get). Read repository tag. Returns details for a specific tag in the specified repository. This operation accepts bearer tokens issued from organization access tokens (OATs). The token must have the required resource access and scopes. The id is the tag name, e.g. `latest`. [GET /v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}]
- **Delete a Docker Hub registry manifest by ID** (Delete). Delete an image manifest (and so every tag pointing at it) from your repository in the Docker registry. The id must be the manifest digest (`sha256:...`, e.g. the `digest` from repository_tags.get), not a tag. Needs a truto_registry_token (truto_registry_token) from registry_tokens.create with `pull,push,delete`. [DELETE https://registry-1.docker.io/v2/&lt;namespace&gt;/&lt;repository&gt;/manifests/&lt;digest&gt;]
- **Get single Docker Hub registry manifest by ID** (Get). Get an image manifest from the Docker registry by tag or digest: for multi-platform images an index listing each platform (os/architecture) with its digest, otherwise the config and layer digests and sizes. A 404 (MANIFEST_UNKNOWN) means the tag or digest does not exist, so this also checks whether an image exists. Counts as a pull against Docker's pull rate limit. The id is a tag (e.g. `latest`) or a digest (`sha256:...`). Needs a truto_registry_token with `pull`. [GET https://registry-1.docker.io/v2/&lt;namespace&gt;/&lt;repository&gt;/manifests/&lt;reference&gt;]
- **List all Docker Hub registry tags** (List). List the tags of a repository straight from the Docker registry (registry API, lexical order). Page with `n` (page size) and `last` (the last tag of the previous page). Needs a truto_registry_token from registry_tokens.create with `pull` for this repository. [GET https://registry-1.docker.io/v2/&lt;namespace&gt;/&lt;repository&gt;/tags/list]
- **Create a Docker Hub registry token** (Create). Get a Docker Registry bearer token for one repository (OAuth2 password grant at auth.docker.io, using the connected username and token or password). Registry tokens are scoped to a single repository and expire after 300 seconds. Pass the returned access_token as truto_registry_token to registry_tags.list and registry_manifests.get/delete for the same repository. actions: `pull` to read, `pull,push,delete` to delete manifests in your own repository. [POST https://auth.docker.io/token]
