---
title: "sentry"
description: "Investigate and triage production errors with Sentry: issues, events, regressions, and performance, via Sentry's official hosted MCP endpoint."
canonical: https://agentpluginsdirectory.com/plugins/sentry--hiai-gg
last-updated: 2026-09-22
---

# sentry
Investigate and triage production errors with Sentry: issues, events, regressions, and performance, via Sentry's official hosted MCP endpoint.
- Slug: sentry--hiai-gg
- Publisher: HiAI
- Repository: https://github.com/HiAi-gg/agent-plugins
- Manifest: plugins/sentry/plugin.json
- Version: 0.0.2
- License: MIT
- Category (editorial): devops-cloud
- Skills: 4 (analyze-error, investigate-performance, investigate-regression, triage-sentry-issue)
- MCP servers: 1 (sentry)
- Stars: 1
- Repository created: 2026-08-08
- Repository last pushed: 2026-09-03
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/sentry--hiai-gg
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What sentry does, in the publisher's words

Investigate and triage production errors with Sentry: issues, events, regressions, and performance, via Sentry's official hosted MCP endpoint.

An Agent Plugin (spec 1.0.0).

A plugin that pairs Sentry's official hosted MCP endpoint with four skills that teach a disciplined investigation order:

- triage-sentry-issue: assess impact and prioritize.
- investigate-regression: find what changed when an error spiked.
- analyze-error: full end-to-end root-cause workflow.
- investigate-performance: find the slow/failing step in a trace.
- First-party upstream: Sentry's hosted MCP endpoint (mcp.sentry.dev).
- No credentials in the plugin: authentication is the MCP host's OAuth flow, per Agent Plugins v1 design.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/HiAi-gg/agent-plugins/HEAD/plugins/sentry/README.md

## Skills

- analyze-error: Debug a production error end to end from a Sentry issue: read the events, stack and context, breadcrumbs, and values, then produce a diagnosis with a proposed next action. Use when asked to root-cause a production exception.
- investigate-performance: Analyze a Sentry trace or performance span to find the slow or failing step in a request: spans, durations, dependencies, and errors. Use when investigating latency, timeouts, or which service a failure originates from.
- investigate-regression: Determine whether a Sentry issue is a regression and find what changed: compare event timing against releases, find the introducing commit or deploy, and narrow the cause. Use when an error spiked or reappeared after a deploy.
- triage-sentry-issue: Triage a Sentry issue: assess impact, frequency, affected users, and severity from issue metadata, then recommend a priority. Use when asked what to fix first or whether a Sentry error is serious.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- sentry: transport: streamable-http; url: https://mcp.sentry.dev/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.