# Sentry Monitoring MCP > Sentry gives your AI agent full, real-time access to your application's error logs and performance data. Instead of manually navigating dashboards to find crashes or stack traces, you simply ask your agent a question. It pulls the latest exceptions, diagnoses specific issues by feeding it context, and even marks resolved bugs as handled—all from within any MCP-compatible client. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Tags:** error-tracking, performance-monitoring, debugging, stack-trace, incident-management ## Description This connector puts Sentry's entire operational monitoring suite directly into your chat window or IDE. You stop spending time combing through rigid crash dashboards just to figure out what broke last night. Your AI agent now treats your application logs like a searchable database, giving you immediate access to raw exceptions and the full stack trace context for any issue. Need to know why a specific endpoint is throwing fatal alerts right now? You can ask your agent to list all current problems or dive deep into an existing bug using its ID. The system pulls the environmental metadata and reads the entire stack trace, telling you exactly which lines of code need attention. Plus, if you've deployed a fix, you can tell the agent to close out that exception record—marking it resolved without having to click through the web interface. This level of direct control over production data is what Vinkius makes possible. ## Tools ### delete_issue Permanently removes an issue record from Sentry. Use with caution as this action cannot be undone. ### list_events Retrieves a chronological list of recent activity and events for a specific project. ### get_event_details Pulls comprehensive details about one particular event, including all associated metadata. ### list_organizations Displays a list of all Sentry organizations you have access to within the system. ### list_projects Retrieves all software projects contained within a specified organization. ### resolve_issue Changes an issue's status to resolved, safely marking it as handled without needing the web interface. ### list_organization_teams Displays a list of all operational teams configured within your Sentry account. ### list_organization_users Retrieves every user registered across the entire organization's scope. ### get_issue_details Fetches detailed information about a specific recorded bug or issue ID. ### list_issues Lists all active errors and open incidents within a designated project scope. ## Prompt Examples **Prompt:** ``` Enumerate the most recently flared active open errors across the 'frontend-ui' project portal in Sentry. ``` **Response:** ``` I've successfully interrogated the Sentry API via `list_issues` scoping specifically down to the 'frontend-ui' project slug. Your dashboard flags 5 overarching unhandled exceptions aggressively repeating. The paramount threat ranks an ID marking 'TypeError: Cannot read properties of undefined (reading 'auth_token')' with ~4,200 events escalating in merely six hours. Should I invoke the agent to dig deep into this specific issue details block? ``` **Prompt:** ``` Fetch all pertinent internal parameters regarding issue id 6B3VX4921. ``` **Response:** ``` After meticulously scanning via `get_issue_details` parameter boundaries, issue block 6B3VX4921 centers around a PostgreSQL Deadlock collision error. The stack trace isolates its organic foundation originating from your `payment_processor.ts` dependency specifically on Line 132. Over 300 users were severely impacted since Tuesday. Noticeably, this fault correlates concurrently with a massive migration you pushed recently. ``` **Prompt:** ``` I've deployed a patch fixing the deadlock in db.ts. Mutate this specific issue globally to 'resolved'. ``` **Response:** ``` Got it. I've initiated an asynchronous payload signaling tool `resolve_issue` applied effectively corresponding to your specified ID within the active ecosystem. Subsequent polling shows this entity has correctly adopted the formal status value: 'RESOLVED'. Sentry charts will stop screaming out and notifying on channel hooks. ``` ## Capabilities ### Check for active crashes The agent lists currently malfunctioning endpoints and functions, flagging fatal alerts in real time. ### Diagnose specific errors You provide an issue ID, and the agent retrieves the full stack trace along with environmental data for deep analysis. ### View project structure The agent lists all projects or teams configured within your Sentry account. ### Close resolved bugs You instruct the agent to mark a specific issue as handled, updating its status without manual web interaction. ## Use Cases ### Pinpointing a mysterious production failure A developer notices high latency. They ask their agent to list_issues across the affected project. The agent replies by showing 5 repeating 'TypeError' alerts, allowing the developer to immediately use get_issue_details on the top alert ID for the precise code line. ### Managing post-deployment cleanup The DevOps team pushes a patch and knows an old bug is fixed. They prompt the agent, 'Mark this issue as resolved.' The agent uses resolve_issue, updating the record instantly and stopping the alerts. ### Auditing user access after a security incident A manager needs to know who has access to sensitive data. They ask the agent to list_organization_users, getting an immediate roster of all accounts in the entire organization. ### Debugging multi-service interactions The engineer suspects a conflict between two services. They prompt the agent to list_projects and then get_event_details for both projects' latest events, correlating the timestamps to find the collision point. ## Benefits - Get instant visibility into active errors. Instead of clicking through pages, you ask the agent to run list_issues and immediately see which endpoints are throwing fatal alerts. - Deeply analyze crashes without leaving your chat client. By sending an issue ID for get_issue_details, your AI agent devours the full stack trace and environmental context, pointing out exactly where the code failed. - Automate bug lifecycle management. You can use resolve_issue to safely close records once a fix is deployed, eliminating manual status updates in the web dashboard. - Understand system scope quickly. Use list_projects or list_organization_teams to map out which software branches and teams exist across your entire organization structure. - Speed up incident response. When an error occurs, you don't need to copy a massive stack trace into a ticket; the agent pulls the complete details for you. ## How It Works The bottom line is that your AI client acts like a direct API wrapper, turning complex monitoring tasks into simple conversation prompts. 1. Activate this MCP in your workflow configuration and securely provide your organization slug alongside your authentication token. 2. Prompt your AI client with a natural language question, such as 'What errors are happening on the user profile service right now?' 3. The agent executes the necessary tool calls to gather data (like listing issues or getting details) and presents the findings directly in the chat. ## Frequently Asked Questions **Can Sentry MCP list all active open bugs?** Yes, you can use list_issues to retrieve a comprehensive roster of every currently flagged error within a specific project. This lets you see which endpoints are throwing fatal alerts right now. **How do I get full stack trace details using Sentry MCP?** You provide the agent with an issue ID, and it uses get_issue_details to pull every piece of metadata available, including the entire stack trace. This is crucial for debugging. **Is deleting issues via Sentry MCP permanent?** Yes, using delete_issue permanently removes an issue record and this action cannot be reversed. Use it only after confirming you no longer need the data. **Can I find out what projects are configured in my account?** Absolutely. You can use list_projects to get a clean list of every project within your organization's silo, helping you scope your investigation correctly. **Does Sentry MCP help with team structure? ** Yes, the agent provides tools like list_organization_teams and list_organization_users, allowing you to map out who is on which team within the organization.