Direct answer: Finta's catalog currently lists https://mcp.sentry.io/mcp/, while Sentry's current first-party MCP repository points users to https://mcp.sentry.dev. The page should explain Sentry's documented MCP capabilities, but publication and setup instructions must wait until the catalog endpoint is reconciled and a live Aurora receipt is captured.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Sentry remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
Current connection note: The enabled Aurora catalog currently uses mcp.sentry.io, while Sentry's current first-party documentation points to mcp.sentry.dev. The public page names that discrepancy and does not claim a generally available verified connection.
How the Sentry connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.sentry.io/mcp/ |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Sentry remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Inspect authorized Sentry organizations, projects, teams, issues, events, and traces using documented tools.
- Search incident evidence and prepare a source-linked debugging summary.
- Use Sentry's inspect capability for a read-oriented workflow.
- Enable triage or write skills only when the required scopes and a reviewed action are present.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Sentry
Investigate an investor-demo failure
Outcome: Have engineering approve any external explanation and remediation claim.
- Find the affected Sentry project, issue, event, and trace.
- Separate observed evidence from suspected root cause.
- Prepare a concise internal incident brief with source links.
- Have engineering approve any external explanation and remediation claim.
Human decision: Aurora should not mark an incident resolved or tell an investor the issue is fixed without production verification.
Prepare reliability context for a board update
Outcome: Have the engineering owner approve the final board language.
- Retrieve the agreed issue or project evidence for the reporting period.
- Identify recurring classes, open high-impact issues, and known data gaps.
- Draft a source-linked risk summary without inventing uptime or resolution metrics.
- Have the engineering owner approve the final board language.
Human decision: Sentry evidence is one source. It does not establish complete system reliability or customer impact by itself.
How to connect Sentry to Aurora
- Do not publish a connect button until Finta reconciles the catalog URL with Sentry's current official remote endpoint.
- After reconciliation, open Apps in Aurora and select Sentry.
- Authorize the intended Sentry organization and review project, team, event, and write scopes.
- Confirm discovered tools and start with an inspect or read-only issue lookup.
- Enable any triage action only in a controlled test after explicit approval.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Use the smallest Sentry organization, project, team, and event scopes available. Keep inspection read-only by default. Require engineering approval for triage, assignment, status, comment, or remediation changes, and do not expose event payloads or personal data outside the authorized audience.
Limitations to understand
- The audited Finta catalog endpoint conflicts with Sentry's current first-party remote endpoint guidance.
- Sentry's MCP server is optimized for human-in-the-loop debugging, not complete API coverage.
- Available tools and AI search behavior vary by deployment, scopes, and self-hosted configuration.
- Issue evidence can contain secrets or personal data and needs careful handling.
Verification checklist
- Reconcile https://mcp.sentry.io/mcp/ with Sentry's current https://mcp.sentry.dev guidance before publication.
- Complete OAuth in Aurora and capture the effective organization, project, team, and event scopes.
- Capture the discovered tools and compare them with Sentry's current MCP repository.
- Run one safe inspect or read-only issue lookup and retain the receipt.
- Test a triage write only with approval, then verify Sentry's audit trail and record the verification date.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Sentry official MCP documentation (github.com)
- Sentry official MCP documentation 2 (github.com)
- Sentry official MCP documentation 3 (github.com)
- Sentry official MCP documentation 4 (docs.sentry.io)
- Sentry official MCP documentation 5 (docs.sentry.io)