NewJobs: scheduled actions created from chat, personal or shared.Learn more

Sentry + Memtro

Ask what is breaking in production and get the stack trace, not a dashboard.

Connect Sentry and Memtro can search your issues with Sentry's own query syntax, pull the latest event with its exception chain and breadcrumbs, show whether an error is still happening and who it affects, and relate errors to the release that introduced them. Works with sentry.io and self-hosted Sentry.

What you can do with Sentry in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Sentry tool, reads what it needs, and answers with the source cited.

01

What is breaking

Ask what new errors appeared in production in the last day and get the issues with their stack traces, not a dashboard.

02

Which release

Which release introduced the checkout timeout, and which customers hit it.

  • Search unresolved, new or regressed issues per project or across the organisation
  • Read an issue's latest event: message, culprit, tags, affected user and the relevant stack frames
  • List recent occurrences of an issue with environment, release, URL and browser
  • See releases with deploy dates, new issues introduced and authors
  • Resolve short IDs like BACKEND-12A straight from a Slack message or ticket
  • Read-only: never resolves, assigns or changes anything in Sentry

Ask it like this

Questions people ask once Sentry is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.

  • ›What new errors appeared in production in the last 24 hours?
  • ›Show me the stack trace for BACKEND-12A.
  • ›Is the checkout timeout error still happening, and which customers hit it?
  • ›Which release introduced the most new issues this month?

Where it fits

Teams that get the most from Sentry in Memtro, with the rest of their stack attached.

Better together

A record in Sentry 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

  1. 01In Sentry, go to Settings → Developer Settings → Organization Tokens (or your account's Auth Tokens) and create a token with org:read, project:read and event:read
  2. 02In Memtro, open Connections → Sentry, paste the token and your organisation slug (the part after sentry.io/organizations/)
  3. 03Self-hosted? Add your instance URL as the base URL. Memtro verifies access to the organisation and saves the connection
Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Sentry tools are the same everywhere.

Clients and agents →

Questions

Can Memtro change anything in Sentry?
No. The Sentry connector is read-only: every tool reads, searches or lists. Nothing is created, sent, updated or deleted, and the credentials you give it should be read-only too.
Who can use a Sentry 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 Sentry 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.
How do I connect Sentry?
Auth token. In Sentry, go to Settings → Developer Settings → Organization Tokens (or your account's Auth Tokens) and create a token with org:read, project:read and event:read.

Connect Sentry in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.