Ask GlitchTip which errors are new, how often they happen and where they fail.
Connect GlitchTip with an auth token and Memtro reads projects, issues with status, level, event and user counts and when first and last seen, and one issue's latest stack trace and comments. User, request and cookie data are never read, and the token acts as you, narrowed by its scopes. When you ask, and once an administrator has granted them by name, it can comment on, resolve, ignore or assign issues, record releases and deploys, manage uptime monitors, projects and teams, and invite or remove members, which emails the invitee. Deleting an issue, project, release or monitor is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right GlitchTip tool, reads what it needs, and answers with the source cited.
These tools change something in GlitchTip. 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 GlitchTip, choosing the same kinds; the tab shows GlitchTip's own steps. Each event can start a job, with the event as its input. GlitchTip signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce GlitchTip 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.
GlitchTip + MemtroWhich new errors appeared in the checkout project today?
How many users has the payment timeout error affected?
Where in the code does issue CHECKOUT-4F fail?
Resolve CHECKOUT-4F and add a comment saying the fix shipped in 2.14
Record release 2.14 as deployed to production
The engineering lead at Brightwave Ltd asks what broke after Tuesday's release. Memtro lists unresolved issues seen since then: a payment timeout with 312 events from 41 users, and its last stack frames point at the card retry handler.
Dan Fletcher asks Memtro to resolve the timeout issue, note that version 2.14 fixed it, and record the 2.14 deploy to production. With the actions granted, Memtro adds the comment as his token's user, sets the issue to resolved and records the deploy. Nothing is deployed and GlitchTip sends no notification for the comment.
The teams that lean on GlitchTip most, a question each of them asks, and what they connect beside it.
A record in GlitchTip 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
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 GlitchTip open profile menu → Auth Tokens → Create New Token with org:read, project:read and event:read, plus event:write for the comment and issue actions, and copy it: it is shown once
Add project:releases only to record releases and deploys, project:write for projects, monitors and status pages, project:admin to delete a project, team:write for teams, and member:write or member:admin to invite or remove members
In Connections → GlitchTip in Memtro paste the Auth token. Leave Host blank for app.glitchtip.com or type your install's public host name only, and leave Organization slug blank for your first organisation
Ask which new errors appeared in production today
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The GlitchTip tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to an issue; edit a comment's text; delete a comment; resolve, ignore or reopen an issue, or change who it is assigned to; delete an issue; record a release for one or more projects; record a deploy of a release to an environment; delete a release (permanent); create an uptime monitor; change an uptime monitor; delete an uptime monitor (permanent); create a project under a team; rename a project or change its platform or throttle; delete a project with all its issues (permanent); create a team; create a private status page; invite a person to the organization (emails them); remove a member from the organization. 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.
Auth token. In GlitchTip open profile menu → Auth Tokens → Create New Token with org:read, project:read and event:read, plus event:write for the comment and issue actions, and copy it: it is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in GlitchTip, choosing the same kinds; the tab shows GlitchTip'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
