Sentry
Triage Sentry issues, tune alerts, and adjust dashboards from your agent while you fix production errors between feature work.
Overview
com.mcparmory/sentry is a MCP server for the Operate phase that tracks errors, manages performance alerts, and configures Sentry dashboards and monitors from your agent.
What is this MCP server?
- Track and query errors and issues in Sentry projects via MCP
- Manage performance alerts and notification rules from the agent session
- Configure dashboards and monitors without leaving Claude Code or Cursor
- stdio server version 1.0.2: mcparmory-sentry on PyPI (uvx) and ghcr.io/mcparmory/sentry:1.0.2 on OCI
- Published in MCP Armory registry alongside other com.mcparmory integrations
- 2 distribution packages: PyPI mcparmory-sentry and OCI ghcr.io/mcparmory/sentry:1.0.2
- Transport: stdio
Community signal: 25 GitHub stars.
What problem does it solve?
Production fires a Sentry alert and you lose minutes hopping between the Sentry UI and your IDE instead of letting the agent pull context and suggest fixes immediately.
Who is it for?
Indie SaaS and API builders already on Sentry who want Claude Code or Cursor to investigate and configure monitoring during incident response.
Skip if: Greenfield projects with no Sentry SDK yet, or teams that standardize on a different APM with no Sentry org.
What do I get? / Deliverables
Issue context, alert changes, and monitor setup happen in-chat so you can go from stack trace to patch with fewer tab switches.
- Agent-accessible Sentry issue and alert context for faster fixes
- Updated monitors or dashboards reflected in your Sentry org
- MCP Armory package at version 1.0.2
Recommended MCP Servers
Journey fit
Sentry is the default home for production exceptions and performance regressions after ship, which maps cleanly to Operate. Errors subphase is where you inspect stack traces, mute noise, and wire monitors—not where you write greenfield UI.
How it compares
Sentry API MCP for ops triage, not an application logging library skill or a load-testing harness.
Common Questions / FAQ
Who is com.mcparmory/sentry for?
Solo builders and small teams running Sentry in production who want their coding agent to query issues and adjust alerts and dashboards over MCP.
When should I use com.mcparmory/sentry?
Use it during Operate error triage, post-deploy regressions, or when tuning performance alerts and monitors after launch.
How do I add com.mcparmory/sentry to my agent?
Add stdio MCP config for uvx mcparmory-sentry 1.0.2 or ghcr.io/mcparmory/sentry:1.0.2, and set a Sentry auth token with the API scopes your workflows need.