Sentry MCP integration
Investigate production issues, errors, and release health through MCP tools backed by your Sentry organization.
Sentry is one of the strongest operational providers for Connexsus because it turns live issue context into a reusable MCP surface. Agents can inspect errors, look at release state, and accelerate triage without manual dashboard hopping.
Install path
This provider uses a managed OAuth redirect flow. Teams sign in, authorize the workspace, and then enable the provider inside a project.
What you can do with Sentry
- Review top incidents before debugging.
- Map a production error to the release that introduced it.
- Use incident data to guide code or infrastructure remediation.
Sample prompts
Available capabilities
14 toolslist_organizations
List available Sentry organizations for the connected account.
find_organizations
Official Sentry MCP organization listing tool.
list_projects
List projects in a Sentry organization.
find_projects
Official Sentry MCP project listing tool.
search_issues
Search Sentry issues with natural language.
search_events
Search Sentry events/logs/errors with natural language.
search_alerts
Search alert-like incidents via Sentry event search.
get_issue
Get details and stack trace summary for a specific issue.
get_issue_details
Official Sentry MCP issue details tool.
update_issue
Official Sentry MCP issue triage tool (status/assignment).
resolve_issue
Resolve or reopen a Sentry issue.
assign_issue
Assign a Sentry issue to a user/team.
query_seer
Ask Sentry Seer for root-cause analysis of a specific issue.
analyze_issue_with_seer
Official Sentry MCP Seer analysis tool.
FAQ
Does this replace the Sentry UI?
No. It complements the Sentry UI by exposing the most useful incident and issue flows inside MCP tools.
Can public pages show my Sentry issues?
No. Public pages only describe the provider and its use cases.
Who should use Sentry with Connexsus?
Engineering and reliability teams that want faster incident context inside coding or operational agents.
Auth and workspace model
Connexsus separates public provider information from private runtime state. Teams install the provider after sign-in, assign it to a project, and then expose tools to supported MCP clients from one managed gateway endpoint.