Skip to main content
Integration guide

Sentry

Check community bug reports against the errors your telemetry actually recorded.

Connect with
Sentry authorization
Scope
One Sentry organization, per product
Direction
Read-only

Kinn reads Sentry data only and makes no changes to your issues, projects, or alerts.

Sentry is a trusted MCP connector. Kinn connects out to Sentry's own official MCP server and uses the tools Sentry publishes there, so you're always working against Sentry's current capabilities rather than a copy Kinn maintains.

This is the connector that closes the most frustrating gap in bug triage. Community feedback tells you what it feels like — "the game crashes when I open the map" — while Sentry tells you what actually happened, with a stack trace and a count. Separately, each is half a picture. Together they tell you whether a loud complaint matches a real error, and how many users hit it silently without ever posting about it.

What Kinn can read​

The tools come from Sentry's MCP server, so Sentry defines the exact list and it can change as they update it. Broadly, Kinn can search issues and errors, read event details and stack traces, check how often something is occurring and how many users it affects, and review performance data.

Unlike Jira and Linear, this connector is read-only — Kinn investigates in Sentry but files nothing there. When an error needs a ticket, that goes to your issue tracker.

How to connect​

Connecting requires the Editor role or higher on the Kinn account.

  1. Go to Settings → Connections and find Sentry.
  2. Select Connect. You'll be sent to Sentry to authorize access.
  3. Approve the access Sentry requests.
  4. Return to Kinn and ask it about a recent error.

The connection belongs to one Kinn product. If you manage several products, connect Sentry for each one you want it available on — this keeps each product's error data scoped to that product.

Permissions​

  • Sentry's own permissions. Kinn acts through the account that authorized the connection and can only reach what that person can reach.
  • Your Kinn role. Reading Sentry is available to anyone who can use the product. Connecting or disconnecting the integration requires Editor.

To remove access, go to Settings → Connections and select Disconnect.

What you can now ask and do​

  • Players are reporting a crash when opening the map. Is there a matching error in Sentry, and how many users has it hit?
  • We have 40 Discord reports about save corruption. Does Sentry show a matching error, or is this happening silently?
  • What are our top errors by user count this week, and is anyone talking about them in the community?
  • Show me the stack trace for the most frequent crash since the 2.4 release.

The third one is worth running regularly. An error with high volume and no community chatter is often the most dangerous kind: users are hitting it and churning rather than complaining.

Reading the two sources together​

They disagree more often than you'd expect, and each kind of mismatch means something:

  • Loud in the community, quiet in Sentry — often not a crash at all. Usually a design or UX problem people describe as "broken."
  • Loud in Sentry, quiet in the community — users are hitting it and leaving. Prioritize higher than the silence suggests.
  • Loud in both — straightforwardly real and urgent.

If the connection stops working​

Kinn keeps working if Sentry is unreachable — the connector contributes no tools for that conversation and the rest of Kinn is unaffected. If Sentry tools stay unavailable, disconnect and reconnect from Settings → Connections.

Next​