4,500+ servers built on MCP Fusion
Vinkius

Sentry MCP. Run complex error diagnostics from your chat.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Sentry MCP on Cursor AI Code Editor MCP Client Sentry MCP on Claude Desktop App MCP Integration Sentry MCP on OpenAI Agents SDK MCP Compatible Sentry MCP on Visual Studio Code MCP Extension Client Sentry MCP on GitHub Copilot AI Agent MCP Integration Sentry MCP on Google Gemini AI MCP Integration Sentry MCP on Lovable AI Development MCP Client Sentry MCP on Mistral AI Agents MCP Compatible Sentry MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Sentry MCP Server gives your AI agent direct access to Application Performance Monitoring data. You can query raw exceptions, read full stack traces, list current errors across projects, and even close bugs directly from your chat window or IDE.

It turns complex debugging into simple conversations.

What your AI agents can do

Delete issue

This permanently deletes an issue in Sentry. Use this only if you are absolutely sure it should be gone.

Get event details

Retrieves all details for a single, specific system event log entry.

Get issue details

Pulls every piece of data—the full stack trace and metadata—related to one particular bug issue ID.

+ 7 more capabilities included
List all current project issues

The tool list_issues finds and reports on active, recurring errors across a specified Sentry project.

Get detailed error information

Using get_issue_details, the agent pulls all contextual data, including the full stack trace, for one specific issue ID.

List recent system events

The tool list_events retrieves a list of general activity logs that occurred recently in the project.

Identify organizational components

You can use tools like list_projects, list_organization_teams, and list_users to map out who owns what within your Sentry account.

Resolve a flagged bug

The tool resolve_issue changes the status of an issue in Sentry, marking it as fixed or handled.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Sentry MCP Server: 10 Tools for Monitoring & Debugging

These tools allow your AI client to interact directly with Sentry's API. They let you list projects, check status, and pull raw error data without opening the web browser.

delete019d7606

delete issue

This permanently deletes an issue in Sentry. Use this only if you are absolutely sure it should be gone.

get019d7606

get event details

Retrieves all details for a single, specific system event log entry.

get019d7606

get issue details

Pulls every piece of data—the full stack trace and metadata—related to one particular bug issue ID.

list019d7606

list events

Generates a list of recent system events across the entire project's operational timeline.

list019d7606

list issues

Shows all currently open and recurring issues (errors) within a defined Sentry project scope.

list019d7606

list organization teams

Lists every team configured under your main Sentry organization account.

list019d7606

list organization users

Provides a list of all users associated with the entire Sentry organization.

list019d7606

list organizations

Retrieves a catalog of every separate Sentry organization you manage.

list019d7606

list projects

Lists all individual software projects (repositories) configured in your Sentry silo.

resolve019d7606

resolve issue

Changes the status of a bug issue to 'resolved,' marking it as handled within Sentry's tracking system.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Sentry, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

You're giving your AI agent direct access to Sentry’s full Application Performance Monitoring stack. You don't have to waste time digging through dense crash dashboards in a browser; your agent pulls raw exceptions and deep data right into your chat or IDE. This server lets you handle complex debugging like it's just a conversation.

Handling Issues and Bugs:

The tool list_issues runs and reports on every active, recurring error across the specific project scope you define. For any one of those reported issues, you can run get_issue_details, which pulls all the contextual data—the full stack trace and all associated metadata—for that single bug ID. Once you've confirmed it's fixed or handled, running resolve_issue changes its status in Sentry, marking it as resolved without touching a web UI.

Tracking System Activity:

The tool list_events generates a rundown of general activity logs that happened recently across the entire project timeline. If you need to dig into one specific log entry, you run get_event_details and get every piece of data associated with that single system event.

Managing Your Environment:

You can map out your entire organization's structure using several tools. Run list_organizations to get a catalog of every separate Sentry account you manage. Inside those, you use list_projects to list all individual software repositories. To see who runs what, run list_organization_teams to list every team configured under your main organization account; pairing that with list_organization_users gives you a roster of every user associated with the entire Sentry setup.

Taking Action and Cleanup:

Beyond viewing data, you have control over maintenance. You can use delete_issue to permanently wipe an issue from Sentry—you've gotta be absolutely sure it should vanish before running that one. The combination of these tools means your agent handles everything: listing active errors (list_issues), getting deep context on those errors (get_issue_details), seeing general activity logs (list_events), and managing the entire organizational structure (list_projects, list_organization_teams, etc.).

How Sentry MCP Works

  1. 1 Activate this unified Server in your agent's configuration.
  2. 2 Provide your Organization Slug and Auth Token securely to grant access.
  3. 3 Ask your AI client a question, like: 'What are the top 5 open errors in the payments project?'

The bottom line is you don't have to switch apps or navigate dashboards; you just ask your agent to find and analyze the problem.

Who Is Sentry MCP For?

This is for engineers who get frustrated staring at dashboards late at night. It’s for the DevOps engineer who needs a quick, programmatic view of production stability, or the founder who needs an instant summary of critical bugs before a meeting.

Software Engineer

They use get_event_details to fetch the exact variable state that caused a production service failure and feed it directly into their IDE chat.

DevOps Engineer

They command list_issues across multiple servers to see if a recent deploy spike in latency or errors.

Technical Founder

They casually ask the agent for a summary of high-priority, open bugs today before their daily standup call.

What Changes When You Connect

  • Stop manual dashboard clicking. Instead of hunting through web UI tabs, you ask the agent to list_issues and get a summary instantly.
  • Deep context on failure points. The tool get_issue_details feeds the LLM the full stack trace and environment data—no copy-pasting required.
  • Triage bugs without logging in. You can use resolve_issue to mark an exception as safe, handled work directly through conversation.
  • Map your whole infra quickly. Use list_projects, list_organization_teams, and list_users to understand the full structure of your Sentry setup.
  • See what just happened. Run list_events to get a raw feed of recent activity logs, helping you correlate an error with a specific deployment time.

Real-World Use Cases

01

Debugging a production crash in the CI/CD pipeline

A developer finds an intermittent failure. Instead of waiting for a teammate to manually pull data, they prompt their agent: 'Show me all issues related to user authentication.' The agent runs list_issues, pulls one ID with get_issue_details, and presents the full stack trace so the dev can write the fix immediately.

02

Cleaning up old, fixed bugs

The ops engineer has finished investigating a critical bug. They don't want to navigate back into the web portal. The agent runs resolve_issue on the specific ID, closing it and updating the official status without extra steps.

03

Auditing project scope before onboarding

A new team member needs visibility across all services. They ask the agent to 'List all projects under this organization.' The agent runs list_projects and gives them a clear, structured inventory of every silo they need to know about.

04

Correlating errors with user groups

The technical founder suspects only one department is having issues. They ask the agent to 'List all teams.' Then, when an issue pops up, they can narrow the scope by referencing team metadata or running list_issues scoped by project.

The Tradeoffs

Treating the AI like a search bar

Asking the agent vague questions like, 'What's wrong with my app?' This results in generalized answers because it doesn't know where to look.

Always start by scoping your request. Use list_issues first, and then drill down using a specific ID and get_issue_details. Be precise.

Manually copying stack traces

The engineer has to navigate the Sentry dashboard, right-click, copy dozens of lines of code, and paste them into a separate chat window for analysis.

Just tell your agent: 'Get me issue ID [ID] details.' It uses get_issue_details and outputs the entire, clean stack trace directly to your conversation.

Confusing event logs with bugs

Seeing a general system warning on a dashboard and thinking it's a bug that needs resolving.

Use list_events for general activity or deployment warnings. Only use list_issues when you are sure the problem is an unhandled crash or recurring exception.

When It Fits, When It Doesn't

You should use this server if your workflow requires real-time analysis of production failures, error logs, and performance metrics. It’s essential for anyone who needs to move beyond simple status checks into deep debugging.

Don't use it if you just need a simple user list or basic project inventory (though tools like list_users help there). If your goal is merely data logging or tracking non-crash events, check if those logs can be accessed through a general data API rather than needing the full Sentry investigative suite. This tool handles the entire lifecycle: discovery (list_issues), analysis (get_issue_details), and cleanup (resolve_issue).

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Sentry Application Monitoring. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

delete_issue get_event_details get_issue_details list_events list_issues list_organization_teams list_organization_users list_organizations list_projects resolve_issue

Debugging crashes shouldn't mean clicking through ten dashboards.

Today, finding a bug means navigating to the Sentry web interface. You click on 'Projects,' then select the failing service. You filter by date, search for error types, and finally drill down into an issue ID just to see the stack trace. It's slow, it's clicking hell.

With this MCP server, you ask your agent: 'Show me all unhandled exceptions from the payment service.' The agent runs `list_issues` and immediately feeds you the summary. You get the critical data—the full stack trace via `get_issue_details`—without leaving your chat window.

Sentry MCP Server: Get bug status updates instantly.

The old way meant that if a teammate fixed the issue, you had to manually confirm it was resolved in the web UI. This required another set of clicks and confirmation steps just to update the record.

Now, tell your agent: 'Resolve this bug for me.' The agent runs `resolve_issue` instantly, marking the exception as handled across Sentry's entire system. Done.

Common Questions About Sentry MCP

How do I use list_issues to find active bugs? +

To see current issues, ask your agent to run list_issues and specify the project name. This gives you a quick summary of all open errors without needing to navigate the dashboard.

What is the difference between list_events and list_issues? +

list_events provides general system activity logs (like deployments or warnings). list_issues, however, focuses specifically on recurring, unhandled software exceptions that signal a true bug.

Can I close a bug using resolve_issue? +

Yes. You pass the issue ID to the agent and ask it to run resolve_issue. This changes the status in Sentry, marking the problem as fixed or handled.

Does get_issue_details provide the full stack trace? +

Yes. It pulls all contextual data for that specific issue ID, including the entire stack trace and environmental metadata needed to pinpoint the root cause.

How do I use list_projects to understand my application scope? +

It returns a catalog of every project configured in your Sentry organization. This is critical because it lets you identify the exact project slug needed before running any other debugging tool like list_issues or get_event_details.

Does list_organization_users help me track who caused a bug? +

Yes, this tool lists every user within your organization's Sentry environment. You can correlate specific error IDs and stack traces against the user profiles to pinpoint if an issue affects a particular role or employee group.

Is using delete_issue irreversible? +

It is. delete_issue permanently removes the bug report from Sentry's records. Only use this tool when you are 100% certain that the logged exception was erroneous and needs to be purged entirely.

What credentials do I need for any tool in the Sentry MCP Server? +

You must provide your Organization Slug and a valid Auth Token. These two pieces of information establish the secure boundary (or scope) for all operations, ensuring every action—from listing to resolving—only interacts with data from your company's instance.

Can this AI integration actually mark errors as fixed? +

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.

What is the difference between inspecting an 'Issue' and an 'Event'? +

An 'Issue' gathers underlying multiple occurrences of the identical stack exception into one overarching master group. In contrast, querying an 'Event' (get_event_details) focuses the AI on a strictly singular, point-in-time incidence where the system crashed.

Do I need to supply the Organization Slug with every command? +

You configure the overarching Organization Slug strictly at startup globally. For project-level filters, let your LLM query list_projects first to fetch internal slugs naturally into its memory buffer without constant repeated user inputs.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Sentry. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.