Sentry
Give the Sazabi agent tools to browse error events, issues, and project data across your Sentry organizations.
About
This is an MCP connector that gives the Sazabi agent tools from Sentry's hosted MCP server at https://mcp.sentry.dev/mcp. Sentry authenticates via OAuth with dynamic client registration — you authorize once in the browser and Sazabi refreshes the token thereafter. You can optionally scope the connection to a specific organization or project by supplying a path-scoped server URL.
What the agent can do:
- Search and browse Sentry issues and error events
- Inspect stack traces and breadcrumbs
- Navigate organizations, teams, and projects
- Review performance spans and transaction data
Prerequisites
- An active Sentry account (Cloud or self-hosted)
- Member or higher role in the Sentry organization
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Sentry in Settings > MCP connectors.
Authorize
Start the connection. Sazabi redirects you to Sentry to authorize, then back. Optionally, to scope this connection to one organization or project, visit the Sentry MCP page and copy a path-scoped server URL (for example .../mcp/your-org) to paste into the Server URL field before authorizing.
Set up with the CLI
You can also connect Sentry with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
Sentry authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect sentryAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized.
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.
Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.