See it work: a routine built on your production errors
Start the day knowing what broke overnight
Set it up once. Know what broke before standup.
Open Integrations in Town
Go to Integrations in your Town workspace (free to create) and find Sentry.
Authorize the connection
Sign in to Sentry when prompted. Town connects through Sentry's official MCP server (mcp.sentry.dev), so there's nothing to install or configure.
Put your error data to work
Done — ask what's breaking, pull the stack trace behind any issue, and wake up to what broke overnight, already triaged.
Routines that use Sentry
Ready-made routines from the Town library, built on Sentry. Install one and tailor it to how you work.
Just ask your Townie
Sentry holds what broke. Town moves the fix along — briefs, tickets, and answers for the people who never open the dashboard.
“What's breaking in production right now?”
Answered from live issues, events, and stack traces, in plain English.
“Turn that payment timeout into a Linear issue.”
Filed with the stack trace attached, held for your approval.
“What do I tell customers about the checkout errors?”
A plain-English status, drafted from the live issue.
Sentry integration FAQ
The Sentry MCP is Sentry's hosted Model Context Protocol server at mcp.sentry.dev — the official integration surface Sentry maintains. MCP is the open standard that lets AI assistants securely work with data from apps — in this case your issues, events, stack traces, projects, and releases. Town connects to it in one click through Sentry's sign-in; no API keys or local setup.
Town only reads Sentry when you (or a routine you configured) ask for it, and access runs as you — scoped to the organizations and projects your Sentry account can see. Anything Town drafts from that data waits for your approval before it's sent. Read more about how Town approaches security.
Town uses Sentry as a source: searching issues, inspecting stack traces, reviewing projects and releases. And by default, anything externally visible Town does with what it finds — a ticket, an email, a Slack update — is held for your approval first.
The organizations and projects your Sentry account can see. Under the hood these are Sentry's MCP tools: search and inspect issues; review events, stack traces, and spans; and inspect organizations, projects, and releases.
You need a Sentry account and a Town account — free to start. The Sentry connection works on every Town plan.
Sentry's AI debugs inside Sentry. Town connects production errors to the rest of your work — what broke lands in your morning brief, becomes a tracked ticket, and gets explained to the people who never open Sentry.
What is Sentry?
Sentry is how engineering teams watch production — error tracking and performance monitoring that captures every exception, stack trace, and slow span, tied to the release that shipped it.
Sentry captures what broke; Town puts it to work. Connected, overnight errors reach you already triaged, every release gets a verdict, and what's breaking gets explained to the people who never open Sentry.
