Sentry catches errors in production and developer environments. Connecting Sentry to clariBI brings error data into your AI analyses so reliability questions get answered with real signal.
Why connect Sentry
Engineering health metrics (error rate per release, regressions per deploy, top issues by user impact) usually live behind multiple Sentry dashboards.
With Sentry connected, you can ask "Which release introduced the most errors?", "Top 5 issues by user impact in production?", or "Are we seeing an uptick in 5xx after yesterday's deploy?" and get a direct answer.
How the connection works
clariBI talks to Sentry through its hosted MCP server at https://mcp.sentry.dev/mcp. Authentication uses an OAuth flow that clariBI registers itself for (no developer console setup on your side). Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Sentry
U->>C: Click Authorize with Sentry
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
The AI engine selects from these read-only Sentry tools during analyses. None of them modify data in Sentry.
| Tool | Returns | Example question |
|---|---|---|
whoami | The authenticated Sentry user. | Who am I logged in as? |
find_organizations | Sentry organizations the user can access. | Which Sentry orgs am I in? |
find_projects | Projects across orgs. | List Sentry projects. |
find_teams | Teams in an organization. | Which teams own which projects? |
find_releases | Releases tracked in Sentry. | Recent releases in production? |
find_dsns | DSNs (project ingest keys). | List DSNs for the backend project. |
search_issues | Issue search across projects. | Top 10 issues this week. |
search_events | Event search. | Find events from the production environment. |
search_issue_events | Events scoped to a specific issue. | Latest events for issue 12345. |
get_event_attachment | An attachment on an event. | Pull the request body attached to this event. |
get_issue_tag_values | Tag values seen on a specific issue. | Browser tag values on the auth issue? |
get_latest_base_snapshot | Latest snapshot baseline for the project. | Show me the latest snapshot baseline. |
get_profile_details | Profiling sample details. | Show me profile p_001. |
get_replay_details | Session replay details. | Show me the replay for this error. |
get_sentry_resource | Generic resource fetch by URI. | Fetch sentry://issue/12345. |
analyze_issue_with_seer | Seer AI analysis of an issue. | Run Seer analysis on issue 12345. |
search_docs | Sentry documentation search. | How do I configure source maps? |
get_doc | Retrieve a documentation page. | Show me the SDK setup guide. |
use_sentry | Meta-tool for cross-feature operations. | Explore Sentry data for this analysis. |
Data flow during analysis
When you ask a question that maps to Sentry, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Sentry
U->>C: Ask a question about error tracking data
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Sentry card.
- Click Authorize with Sentry.
- Sign in to Sentry in the popup window and grant the requested read scopes.
- Back in clariBI, give your data source a name.
- Click Finish.
Permissions and data access
clariBI requests read access to events, projects, and organizations. No issues can be resolved, no events deleted, and no projects modified. Disconnect from Sentry account settings or from clariBI Settings.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Org-not-found" | You are signed into Sentry as a different account than expected. | Sign out and back in to the correct Sentry account, then reconnect. |