Integrations · Development

Connect Sentry to Well

Name: Sentry entities in Well
Creator: Well

Link Sentry error, release, and user to the customer and revenue context they affect.

What Well pulls from Sentry

Sentry feeds error, release, user into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Sentry’s access.

From Sentry	In Well	Relation
Error	Audit entry	Captures as
Release	Build record	Links to
User	Person	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Sentry → Well

What Well does with your Sentry connection

Connect

Connect Sentry over OAuth (MCP DCR): Well registers a client through Sentry's OAuth Dynamic Client Registration and you approve on Sentry's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings error, release, and user in from Sentry on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Sentry entity into audit entry, build record, and person, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Sentry lands in the workspace as audit entry, build record, and person you can search, chart, and automate.

Questions Sentry unlocks

Ask in plain language. Well answers from your connected Sentry connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Sentry connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Sentry connection…

Connect Sentry in three steps

01
Authorise Sentry via MCP
From Well's Connections panel, search for Sentry and click Connect. Well discovers Sentry's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Sentry's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.sentry.dev/mcp
02
Map your entities
Well's MCP client discovers error, release, and user from Sentry that Sentry's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Sentry records. Because Sentry ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Sentry records happens in the background.

How Sentry stays secure with Well

Well connects to Sentry's MCP server (mcp.sentry.dev/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Sentry secret. Tokens are scoped to the error, release, and user Sentry exposes and refreshed server-side. Reads only, Well cannot modify or delete Sentry records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.sentry.dev/mcp

Read Sentry records
Resources the Sentry MCP server exposes, scoped by your OAuth approval.
granted
Resolve error, release, and user across your stack
Match identifiers in Sentry against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Sentry records
Not granted; Sentry is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Sentry passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Sentry’s admin panel.

Frequently asked questions about Sentry and Well

From Well, open Connections, find Sentry, and click Connect. Well discovers the OAuth metadata at mcp.sentry.dev/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Sentry's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in error, release, and user from Sentry and reshapes each entity into your workspace: error becomes audit entry; release becomes build record. Every record arrives with the source identifier preserved, so Sentry stays the source of truth while Well lets you query the data alongside the rest of your stack.

Every Sentry incident, postmortem, or rollback event carries the affected services, which Well joins to the customer entities those services support. Asking "which customers were impacted by last Tuesday's incident" returns the list with severity, restoration time, and any open follow-up actions per customer.

Well watches for updates to errors and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right audit entry. Edits flow in incrementally; nothing is duplicated, and the Sentry source identifier is retained on every revision.

Well combines live Sentry events with periodic reconciliation reads of error, release, and user. New rows appear within seconds when Sentry pushes them; periodic reads catch anything a push missed. The first connect backfills history from Sentry in the background.

Open Connections > Sentry in Well and click Disconnect. Well calls Sentry's token revocation endpoint and stops calling Sentry immediately on its side; provider-side propagation to Sentry's admin panel varies by provider. The error, release, and user Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Sentry records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.