Sentry

Sentry MCP Connector for Claude

A+

Grant your AI agent full access to Sentry's Application Performance Monitoring tools to track raw exceptions, resolve error logs, and inspect crash stack traces dynamically.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Equip your favorite LLM interface with direct, real-time investigative access over your application's Sentry operational environments. Skip the grueling task of combing through the rigid crash dashboard visually. Now, your AI can pull up the latest software exceptions directly into Cursor or an MCP-enabled chat window, read the contextual stack trace natively, and even close out resolved bugs.

What you can do

  • Live Crash Monitoring — Query the list_issues functionality at any time to instantly see which endpoints or functions are currently malfunctioning and throwing fatal alerts
  • Deep Error Inspection — Feed an issue_id to the agent via get_issue_details. The LLM will devour the entire stack trace, evaluate the environmental metadata, and suggest precisely which lines of code need attention
  • Project & Organization Forensics — Interrogate the AI regarding internal structures (list_users, list_teams) and easily scan separate software branches or repositories (list_projects) configured in your Sentry silo
  • Alert Triage (Mutable) — Dictate the agent to close resolved items (resolve_issue), marking the exception safely as handled without having to load the web interface

How it works

  1. Simply activate this unified Server in your workflow configurations
  2. Provide your overarching Organization Slug alongside your scoped Auth Token securely
  3. Start pinging Claude asking: 'Why did my Vercel app crash 5 minutes ago on Sentry?'

Who is this for?

  • Software Engineers — fetch the specific get_event_details string natively in your IDE, feeding the LLM the exact variable state that shattered the production service
  • DevOps Engineers — command the tool to list_issues occurring across European servers and quickly ascertain if a recent deploy caused a spike in latency
  • Technical Founders — casually ask the chatbot for a summary of high-priority bugs open today across all startup projects before the daily standup
error-trackingperformance-monitoringdebuggingstack-traceincident-management

10 tools expose this connector's capabilities to your AI agent.

delete_issue

This action is irreversible. Permanently deletes an issue

list_events

Lists recent events for a project

get_event_details

Retrieves details for a specific event

list_organizations

Lists all Sentry organizations

list_projects

Lists all projects in an organization

resolve_issue

This is a reversible side-effect. Resolves an issue in Sentry

list_organization_teams

Lists all teams in an organization

list_organization_users

Lists all users in an organization

get_issue_details

Retrieves details for a specific issue

list_issues

Lists all issues (errors) in a project

See how to talk to your AI agent using Sentry.

Enumerate the most recently flared active open errors across the 'frontend-ui' project portal in Sentry.

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?

Fetch all pertinent internal parameters regarding issue id 6B3VX4921.

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.

I've deployed a patch fixing the deadlock in db.ts. Mutate this specific issue globally to 'resolved'.

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.

Yes. This agent component possesses mutable write access. If you invoke the prompt properly, it will fire the `resolve_issue` tool, marking the corresponding exception ID completely dealt with inside the Sentry ecosystem. It can also erase bugs fully via `delete_issue`.

Related Connectors