# Sentry Alternative MCP

> Sentry Alternative MCP connects your AI agent directly to application error data, letting you monitor system health and debug issues without leaving your chat window. Query full stacktraces, check deployment versions, and audit alert rules from any MCP-compatible client.

## Overview
- **Category:** loved-by-devs
- **Price:** Free
- **Tags:** error-tracking, performance-monitoring, application-health, debugging, alerting, issue-management

## Description

Your app is breaking, and the dashboard is a nightmare of clicks. This MCP changes that by giving your AI agent real-time access to all your application errors. Instead of switching between tabs to find out what went wrong, you just ask your agent to look into it. It pulls raw error events with full stacktraces and context—like HTTP headers and user data—so you can debug the root cause immediately.

It lets you track which version of code caused a problem by listing all deployments. You can also get a complete picture of your team's notification system, reviewing every configured alert rule to make sure no critical issue gets missed. If you use Vinkius, you connect this MCP alongside thousands of others, giving your agent one central place to manage observability and debugging.

It’s like having an on-call engineer sitting next to you, ready to pull up the data whenever a problem pops off.

## Tools

### list_alert_rules
Retrieves a list of all configured alerts, detailing their conditions and actions (like sending an email or Slack message).

### get_auth_info
Checks if your integration token is active and correctly connected to the Sentry account.

### list_events
Lists recent error events for a specific project, providing key details like timestamps and basic stacktrace snippets.

### get_event
Fetches the full, detailed record for an event ID you obtained from listing recent errors.

### get_issue
Gets comprehensive details about a specific issue using its unique numeric identifier.

### get_project
Retrieves the full configuration and metadata for any specified project within your organization.

### get_release
Pulls all deployment metadata for a specific version string, linking it to the organization.

### list_issues
Lists issues across your organization or scoped to one project; you can filter results by status or priority.

### list_organizations
Retrieves a list of all organizations you belong to, providing their unique slugs for subsequent calls.

### list_projects
Lists every application or service project within your organization, requiring the parent organization slug.

### list_releases
Gets a list of all deployed versions for an organization or a specific project to track history.

### search_issues
Searches issues using Sentry's query syntax, allowing you to narrow results by text, priority, or status across projects.

### list_tags
Displays all available tags used for categorization within a specific organization or project.

### list_teams
Lists the various teams within your organization, using the organization slug to scope the results.

### update_issue
Changes the status or adds/removes tags from an existing issue using its numeric ID.

## Prompt Examples

**Prompt:** 
```
Show me all unresolved issues in my backend-api project.
```

**Response:** 
```
I've scanned your backend-api project and found 4 unresolved issues. The most critical is a `ZeroDivisionError` in payment processing (127 events in the last 24h). Would you like the full stacktrace?
```

**Prompt:** 
```
Which releases have been deployed for my organization in the last month?
```

**Response:** 
```
I've retrieved 6 releases for your organization. The most recent is `v2.14.3` deployed 2 days ago to the production environment. The oldest in this window is `v2.12.0` from 28 days ago. Would you like event counts per release?
```

**Prompt:** 
```
What alert rules are currently configured for the mobile-app team?
```

**Response:** 
```
Your mobile-app project has 3 active alert rules: 1) Notify #eng-mobile on Slack when a new issue is created, 2) Send email to oncall@company.com when issue count exceeds 100 in 5 minutes, 3) Create PagerDuty incident for errors with priority 50. Would you like the full configuration details for any rule?
```

## Capabilities

### Inspect Raw Error Events
Retrieve complete details for specific errors, including stacktraces and user context.

### Search and Group Issues
Filter across all projects or the entire organization to find unresolved issues based on status or priority.

### Track Deployments and Releases
List every version deployed, allowing you to link specific bugs back to their source code release.

### Audit Alert Rules
Review all active notification rules (for Slack, email, PagerDuty) across your organization's projects.

### Update Issue Statuses
Change the status of a reported issue or assign it to another team member directly through conversation.

## Use Cases

### Debugging a production failure
A developer notices high error rates in the payments service. They ask their agent to list recent events for that project, find the specific `ZeroDivisionError`, and use get_event to pull the full stacktrace, identifying the line of code responsible.

### Auditing team coverage
An EM needs to know if the on-call rotation is covered for all critical services. They ask their agent to list projects and then use list_alert_rules to confirm that every core service has a corresponding PagerDuty trigger.

### Investigating stale issues
A team member suspects an old bug is still open. Instead of browsing manually, they ask the agent to search issues using specific query syntax and get_issue details on the top result to verify its current status.

### Checking deployment impact
The product team needs to know if a new feature caused an issue. They prompt their agent with the date range, which triggers list_releases and then allows them to search issues scoped only to that specific version.

## Benefits

- Stop manually opening the dashboard. Instead, ask your agent to list recent events or search issues by priority status, getting instant answers without context switching.
- Pinpoint regressions fast. By calling get_release and viewing deployment metadata, you can correlate a specific bug directly back to the version that introduced it.
- Review notification paths completely. Use list_alert_rules to audit every single rule—from Slack messages to PagerDuty triggers—to ensure your team gets timely warnings.
- Deep dive debugging is easier. The agent pulls full event details, giving you complete stacktraces and user data via get_event, far beyond what a simple dashboard view shows.
- Manage the cleanup process. You can update an issue's status or assign it to someone else using update_issue, keeping your project records accurate without needing to click into the UI.

## How It Works

The bottom line is that your agent handles the complex API calls and delivers clean, actionable information right where you're working.

1. Subscribe to this MCP and enter your Sentry Internal Integration Token.
2. Your AI client verifies the connection, giving you immediate access to organizational settings.
3. You ask a natural language question—like 'Show me all unresolved payment errors from last week'—and receive structured data directly.

## Frequently Asked Questions

**How do I check the status of a bug using Sentry Alternative MCP?**
You can use list_issues to see all open bugs across your organization. If you need details on one specific issue, use get_issue with its numeric ID.

**Can I find out which code version caused the error using Sentry Alternative MCP?**
Yes, run list_releases to see all deployed versions. You can then reference those versions when searching issues or getting details for a specific project release.

**What if I need to know who gets notified when things break with Sentry Alternative MCP?**
You run list_alert_rules. This tool shows you all configured alerts, letting you audit the conditions (e.g., issue count > 100) and the resulting actions (Slack, email).

**Is Sentry Alternative MCP good for debugging stacktraces?**
Absolutely. Use get_event to retrieve raw error events that include complete stacktraces, breadcrumbs, and all relevant HTTP context.

**Does the Sentry Alternative MCP allow me to change an issue's status?**
Yes, you can use update_issue. This allows your agent to change the status of a bug or assign it to another team member without manual UI clicks.