Sentry
The Sentry connector gives AI agents the ability to search and triage errors, inspect event stack traces, track releases, and update issue status — all via the Sentry REST API. Sentry uses API key authentication: paste your Sentry auth token when connecting, and MCPGate stores it encrypted in its vault.
Authentication#
Sentry uses API key authentication. To connect:
- Sign in to Sentry and navigate to Account Settings → API Tokens
- Click Create New Token
- Grant the scopes listed below, then copy the generated token
- Paste it into the API Key field in MCPGate's connector setup form
Note
Grant the following scopes when generating the token.
| Scope | Purpose |
|---|---|
| project:read | List projects and read project metadata |
| event:read | Read issues and events |
| event:write | Update and resolve issues |
| event:admin | Delete issues |
Tool reference#
The Sentry connector exposes 10 tools. Use the MCP Apps page to enable or disable individual tools per app, and the Guardrails page to add fine-grained rules on top.
| Tool | Category | Description |
|---|---|---|
| sentry_list_projects | read | List all Sentry projects for the authenticated organization |
| sentry_list_issues | read | List issues (error groups) for a Sentry project |
| sentry_get_issue | read | Get a specific Sentry issue by ID |
| sentry_list_events | read | List events for a specific Sentry issue |
| sentry_get_event | read | Get a specific event by project and event ID |
| sentry_list_releases | read | List releases for a Sentry project |
| sentry_search_issues | read | Search for issues in a Sentry project using a query string |
| sentry_update_issue | write | Update a Sentry issue (e.g., assign, change status) |
| sentry_resolve_issue | write | Mark a Sentry issue as resolved |
| sentry_delete_issue | delete | Permanently delete a Sentry issue |
Issue deletion is permanent
sentry_delete_issue permanently removes the issue and all its associated events. This cannot be undone. Deny this tool in any app that does not explicitly require it.Common guardrail recipes#
Read-only access#
Enable only the seven read tools. Deny sentry_update_issue, sentry_resolve_issue, and sentry_delete_issue. Useful for error monitoring dashboards and agents that surface issue context without taking action.
Triage preset#
Enable read tools plus sentry_update_issue and sentry_resolve_issue. Deny sentry_delete_issue. This lets the AI assign and close issues during an on-call rotation without destructive access.
Restrict to specific projects#
Apply the allow_values template to sentry_list_issues and sentry_search_issues. Target the project_slug field and provide a list of project slugs the agent may query.
Troubleshooting#
- Organization slug required— Most Sentry API endpoints are scoped to an organization slug. MCPGate retrieves this automatically on connect. If you see "organization not found", disconnect and reconnect to refresh the cached organization slug.
- Issue ID format — Sentry issue IDs are numeric strings. Do not confuse them with short codes like
PROJ-123shown in the UI — those are display references, not IDs. - Token insufficient permissions — If tools return 403, the auth token was created with insufficient scopes. Generate a new token with the required scopes listed above and reconnect.