Ask Octopus Deploy which release is in production, and what failed to deploy.
Connect Octopus Deploy with your server's host name and an API key and Memtro reads which release is deployed to which environment and whether it succeeded, projects, releases with their notes, deployments, tasks with their outcome and errors, environments, and the audit log. Task logs and change diffs are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can create a release and deploy it to named environments or tenants, running the real deployment steps, cancel or re-run tasks, and permanently delete a release.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Octopus Deploy tool, reads what it needs, and answers with the source cited.
These tools change something in Octopus Deploy. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Octopus Deploy, choosing the same kinds; the tab shows Octopus Deploy's own steps. Each event can start a job, with the event as its input. Octopus Deploy sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Octopus Deploy 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 version of the API is in production?
What failed to deploy this week, and why?
Who deployed to production yesterday?
What are the release notes for the latest checkout release?
Deploy release 4.13.0 of the Acme portal to Production
Before a customer call the account lead asks which version of the Acme portal is in production. Memtro reads the dashboard: release 4.12.0 succeeded in Production on Tuesday, while 4.13.0 is in Staging and its deployment is still running.
Once Staging checks pass, Priya Sharma asks Memtro to deploy Northwind API release 2.8.1 to Production. Memtro starts the deployment, which runs the project's real steps against the production targets and fires its Slack and email notifications, and reports the task so it can be watched or cancelled.
The teams that lean on Octopus Deploy most, a question each of them asks, and what they connect beside it.
A record in Octopus Deploy 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
ZenhubIn Octopus open your profile picture → Profile → My API Keys → New API key, name it Memtro and copy the key, which starts API-. The key can never do more than its user: choose Read-only access for reading only, or give the user ReleaseCreate, DeploymentCreate and TaskCancel on the projects and environments Memtro may act on
In Memtro open Connections → Octopus Deploy and type the Octopus server host as in your browser, acme.octopus.app on Octopus Cloud or your own server's name, with no https://, then paste the API key
Add a Space id such as Spaces-2 only if the projects are not in your default space, and connect. A server only reachable inside your network cannot be reached
Ask which version of the API is in production
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Octopus Deploy tools are the same everywhere.
Only when you ask, and only what it has been granted: create a release of a project; deploy a release to one or more named environments, now or at a set time; deploy a release to named tenants or tenant tags in one environment; cancel a queued or running task, such as a deployment; re-run a finished non-deployment task, such as a runbook run; move a queued task to the top of the queue; replace a release's notes; record a defect against a release, which can stop it being promoted; resolve a release's defect; delete a release with its deployments and tasks, permanently; create an environment. 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.
Octopus server and API key. In Octopus open your profile picture → Profile → My API Keys → New API key, name it Memtro and copy the key, which starts API-. The key can never do more than its user: choose Read-only access for reading only, or give the user ReleaseCreate, DeploymentCreate and TaskCancel on the projects and environments Memtro may act on.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Octopus Deploy, choosing the same kinds; the tab shows Octopus Deploy's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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
