01
Weekly ops review
An engineering manager asks for last week's incidents. Memtro lists them with severity, lead and time to resolve, pulls the outstanding follow-ups and names the owners, ready to paste into the review doc.
incident.io + Memtro
Every incident, its timeline, owners and follow-ups, remembered and searchable.
Memtro connects to incident.io with a read-only API key. It lists incidents by status, severity and date, reads a single incident's roles, timestamps, update log and timeline, tracks outstanding follow-ups and actions, tells you who is on call now, and resolves responders from the user directory. Each hour it records incidents that were declared or resolved so your company memory keeps the operational history.
What you can do with incident.io in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right incident.io tool, reads what it needs, and answers with the source cited.
02
Handover at shift change
The incoming on-call asks what is open. Memtro shows the live incidents, their latest updates, and who is on the schedule now and next, with links to each incident's Slack channel.
- Incidents filtered by status category, severity, date and text
- Full incident view: roles, timestamps, updates, timeline, follow-ups, actions, post-mortem link
- Outstanding follow-ups across incidents by owner
- On-call schedules: who is on now, next, and shifts in a window
- Responder directory by name or email
- Hourly memory of incidents declared and resolved with lead and duration
Ask it like this
Questions people ask once incident.io is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
- ›Which incidents are live right now and who is leading them?
- ›Summarise INC-412 with its timeline
- ›What follow-ups are still outstanding from last month's incidents?
- ›Who is on call for the platform schedule tonight?
- ›How many major incidents did we have this quarter and how long did they take to resolve?
- ›Which incidents mention the payments database?
Where it fits
Teams that get the most from incident.io in Memtro, with the rest of their stack attached.
- EngineeringKeep decisions from evaporatingDecisions, owners and deadlines are extracted from conversations and tool results into a typed, time-aware memory. Corrections supersede old facts instead of piling up next to them.
- ProductHear what customers actually ask forFeature requests are scattered across tickets, call notes, Slack threads and issues. Memtro reads them where they live, links them to the customers who raised them, and remembers which decision closed each one.
- Agent buildersMemory and tools for the agents you buildPoint your own agent at Memtro over the OpenAI-compatible API or MCP and it gets long-term memory, connectors that read by default and act where you grant it, and model routing without you building any of it.
Better together
A record in incident.io is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
How to connect
- 01In incident.io open Settings → API keys and click Add new
- 02Grant only the read permissions (View data, and View on-call schedules if you want on-call)
- 03In Memtro choose incident.io and paste the key
- 04Click Test and connect
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The incident.io tools are the same everywhere.
Set it up as an MCP server →Clients and agents →Questions
- Can Memtro change anything in incident.io?
- Not yet. Today every incident.io tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
- Who can use a incident.io connection?
- 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.
- Does Memtro store my incident.io data?
- 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. An hourly sync anchors recently changed incident.io records into memory as entities.
- How do I connect incident.io?
- API key. In incident.io open Settings → API keys and click Add new.
Connect incident.io in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.