What is broken
The on-call engineer asks why the Acme checkout app is degraded. Memtro reads its resources and events and answers that one deployment is in a crash loop after the image pull for revision 4f2a1c failed at 08:12.
Ask Argo CD what is out of sync, what is degraded, and what was deployed today.
Connect Argo CD with a token and Memtro reads applications with their sync and health status, resources, history and events, who committed a deployed revision, projects and clusters. Cluster and repository credentials, manifests and Helm values are never read. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can sync or roll back an application, which deploys to its cluster, point it at another revision, stop a running sync, restart a resource, create applications, and delete an application or a single resource from the live cluster.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Argo CD tool, reads what it needs, and answers with the source cited.
These tools change something in Argo CD. 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 Argo CD 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.
Which applications are out of sync or degraded?
What was deployed to production today, and who committed it?
Why is the payments app degraded?
Which clusters are registered and how many applications does each run?
Restart the api Deployment in the checkout application
The on-call engineer asks why the Acme checkout app is degraded. Memtro reads its resources and events and answers that one deployment is in a crash loop after the image pull for revision 4f2a1c failed at 08:12.
After a bad release, Dan Fletcher asks Memtro to roll the Northwind api back to yesterday's deployment. Memtro finds it in the history and rolls back, so Argo CD deploys that revision to the cluster for everyone using the service, pruning nothing.
The teams that lean on Argo CD most, a question each of them asks, and what they connect beside it.
A record in Argo CD 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.
An Argo CD administrator adds a local account for Memtro with the apiKey capability in argocd-cm, and grants read access in argocd-rbac-cm, plus applications sync, update, create, action or delete only for the actions Memtro may take
Run argocd account generate-token --account memtro --expires-in 90d and copy the token. A project role's token also works, limited to that project
Open Connections → Argo CD in Memtro, paste the Token and type the Host name only, with no https://, path or port, reachable from the internet with a publicly trusted certificate, not Argo CD's default self-signed one
Ask which applications are out of sync
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Argo CD tools are the same everywhere.
Only when you ask, and only what it has been granted: sync an application to its target revision (deploys to its cluster, never prunes); roll an application back to an earlier deployment (deploys that revision, never prunes); delete an application, leaving its Kubernetes resources running unless cascade is asked for; stop the sync or rollback running on an application; run a resource action, such as restarting a Deployment; point an application at another Git revision (deploys at once if auto-sync is on); delete one Kubernetes resource an application manages; create an application from a repository path or chart (no automatic sync). 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.
Host and Token. An Argo CD administrator adds a local account for Memtro with the apiKey capability in argocd-cm, and grants read access in argocd-rbac-cm, plus applications sync, update, create, action or delete only for the actions Memtro may take.
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