Who pushed latest
Tom Reilly, a DevOps engineer at Acme Ltd, asked who pushed the latest tag to the web image. Memtro read the organization audit log for tag pushes on that repository and gave him the actor, the digest and when it happened.
Who pushed the latest tag to our web image, and when?
Docker Hub holds your container images. Memtro reads repositories in a namespace with pulls, stars, privacy and last update, a repository's tags with size and last push and pull, the organization audit log of who pushed which tag and who changed what, and members, groups and pending invites. When asked and granted, it can create a repository, set immutable tag rules, give a group access to a repository, change or remove members, manage groups, and send, resend or cancel invitations. The audit log, members and invites need an organization owner's token.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Docker Hub tool, reads what it needs, and answers with the source cited.
These tools change something in Docker Hub. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Docker Hub is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Who pushed the latest tag to our web image?
Which repositories in acme have not been updated this year?
Which tags of the api image were not pulled last month?
Who is in the platform group, and with what role?
Give the platform group write access to the api repository.
Tom Reilly, a DevOps engineer at Acme Ltd, asked who pushed the latest tag to the web image. Memtro read the organization audit log for tag pushes on that repository and gave him the actor, the digest and when it happened.
Sarah Chen, an engineering manager at BigCo, asked Memtro to give the platform group write access to the api repository. Memtro granted it, so every member of the group could push to it at once.
The teams that lean on Docker Hub most, a question each of them asks, and what they connect beside it.
A record in Docker Hub is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Docker, open Account settings → Personal access tokens and generate a token, Read-only or Read & Write as you need. An organization owner can instead make a scoped organization access token.
In Memtro, open Connections → Docker Hub and paste the Docker ID or organization name, the Access token and the Namespace to read by default.
An organization token without the repository list scope sees only public repositories, silently. An administrator grants the repository, member and group actions by name to the teams that may use them.
Ask who pushed the latest tag to your web image.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Docker Hub tools are the same everywhere.
Only when you ask, and only what it has been granted: create a repository (public or private, as asked); set a repository's immutable tag rules; give an organization group read, write or admin access to a repository; change an organization member's role; remove a member from an organization; create an organization group; rename a group, change its description or its role; delete an organization group; add a member to a group; remove a member from a group; invite people to an organization by email or Docker ID; resend a pending invitation; cancel a pending invitation. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Docker ID or organization name, access token and namespace. In Docker, open Account settings → Personal access tokens and generate a token, Read-only or Read & Write as you need. An organization owner can instead make a scoped organization access token.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time