Ask which errors are most frequent this week, and whether they followed a deploy.
Connect Airbrake with your User Key and Memtro reads projects with open and resolved error counts, errors with type, message, top backtrace frames and occurrences, each error's occurrences with host and app version, and deploys with revision and who deployed. Request values, sessions and end users' IP addresses are never read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can mute an error so it stops notifying the project's team, unmute it, or permanently delete an error with all its occurrences.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Airbrake tool, reads what it needs, and answers with the source cited.
These tools change something in Airbrake. 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 Airbrake, choosing the same kinds; the tab shows Airbrake's own steps. Each event can start a job, with the event as its input. Airbrake signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Airbrake 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 app has the most open errors?
What is the noisiest error in the checkout project this week?
Did the errors start after yesterday's deploy?
Which hosts and app versions does the TimeoutError come from?
Mute the known Redis timeout error in the billing worker
An hour after a release, the on-call engineer asks whether anything new is breaking. Memtro reads the project's deploys and errors and answers that a NoMethodError first seen at 14:05 follows Dan Fletcher's deploy of revision a41c9e, with 230 occurrences.
The billing worker keeps paging the team about a Redis timeout that has a fix scheduled. Priya Nair asks Memtro to quieten it. Memtro mutes that one error, which leaves the default list and stops notifying the project's team until someone unmutes it. Nothing is deleted.
The teams that lean on Airbrake most, a question each of them asks, and what they connect beside it.
A record in Airbrake 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 Airbrake open the profile menu → Profile settings and copy your User Key. The exact label may differ
Use your own User Key, not a project key, which only sends errors. It acts as you and sees every project you belong to
In Memtro open Connections → Airbrake, paste the User key and connect
Ask which error was the noisiest this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Airbrake tools are the same everywhere.
Only when you ask, and only what it has been granted: mute an error so it leaves the default list and stops notifying the project, or unmute it again; delete an error and all its occurrences permanently. 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.
User key. In Airbrake open the profile menu → Profile settings and copy your User Key. The exact label may differ.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Airbrake, choosing the same kinds; the tab shows Airbrake'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
