Ask Portainer which stacks are running, which environments are down, and who deployed what.
Connect Portainer with your server's host and an access token, and Memtro reads the environments it manages and whether they are up, stacks with status and who deployed them, containers, groups, tags, teams and users on your own server. Stack environment variables are never shown. When you ask, and once an administrator has granted them by name, it can deploy, redeploy, start, stop and delete stacks, start, stop, restart and remove containers, scale or roll back Kubernetes deployments, and add people to teams. These change running services on your servers, and deleting a stack or container is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Portainer tool, reads what it needs, and answers with the source cited.
These tools change something in Portainer. 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 Portainer 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 stacks are not active right now?
Which environments are down?
Who last updated the billing stack, and when?
Which containers on the production host have exited?
Restart the reporting container on staging
The platform lead at Northwind asks why the reporting site is offline. Memtro reads Portainer: the staging environment is up, but the reporting stack is inactive and its three containers exited at 02:15, last updated by Dan Fletcher.
Maya Okafor asks Memtro to start the reporting stack. Memtro confirms the stack and environment, then starts it from its saved definition, so its containers are created and started again on the staging server.
The teams that lean on Portainer most, a question each of them asks, and what they connect beside it.
A record in Portainer 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.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubNeeds Portainer 2.9 or later, Community Edition is enough. Give Portainer a certificate from a public authority (Settings → SSL certificate) or put it behind a reverse proxy that has one
Create a dedicated Portainer user for Memtro with access only to the environments it should see, then your username → My account → Access tokens → Add access token, and copy it: it is shown once. Creating tags, teams and groups needs that user to be an administrator
In Connections → Portainer in Memtro paste the Access token and type your server's name in Host only, with no https://, path or port, and the HTTPS port: 9443 unless behind a proxy on 443
Ask which stacks are not active
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Portainer tools are the same everywhere.
Only when you ask, and only what it has been granted: create a tag in Portainer; delete a tag in Portainer (removed from every environment and group that carries it); start a stopped stack in Portainer (its containers start on that environment); stop a running stack in Portainer (its services go down); delete a stack in Portainer (its containers are removed and the stack definition is gone); deploy a new stack in Portainer from a compose file or git repository (its containers start); replace a Portainer stack's compose file and redeploy it (services restart; the old file is overwritten); redeploy a git-based Portainer stack from its repository (services restart); start a stopped Docker container in Portainer; stop a running Docker container in Portainer; restart a Docker container in Portainer; remove a Docker container in Portainer; force-update a Docker Swarm service in Portainer (its tasks are recreated); scale a Kubernetes deployment in Portainer; roll a Kubernetes deployment back to an earlier revision in Portainer; restart a Kubernetes pod's containers in Portainer; delete a Kubernetes pod in Portainer; create a Kubernetes namespace in Portainer; refresh Portainer's snapshot of an environment; create a team in Portainer; add a user to a Portainer team (gives them the team's environment access); create an environment group in Portainer. 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 access token. Needs Portainer 2.9 or later, Community Edition is enough. Give Portainer a certificate from a public authority (Settings → SSL certificate) or put it behind a reverse proxy that has one.
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
