Plugin · Claude Code · DevOps

Getsentry Sentry Mcp

getsentry-sentry-mcp is a Claude Code plugin for the Operate phase that registers Sentry’s MCP server so agents can search issues, analyze errors, and explore traces via LLM tools.

by getsentry · github.com/getsentry/sentry-mcp

Let your coding agent query Sentry issues, errors, traces, and performance data through MCP instead of context-switching to the Sentry UI during incidents.

623
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install getsentry-sentry-mcp@getsentry/sentry-mcp
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:getsentry/sentry-mcp") and the paste-ready config with skillselion.get_install_config("plugin:getsentry/sentry-mcp").

About

What it does

getsentry-sentry-mcp is a Claude Code plugin packaging Sentry’s MCP server so large language models can interact with your Sentry organization programmatically. Indie builders and small teams already sending events to Sentry gain a second interface: ask your agent to search issues, summarize error spikes, inspect traces, and reason about performance without copying stack traces into chat by hand. The repository is categorized for monitoring and advertises capabilities spanning errors, experimental features, and stable tools, which places it squarely in Operate—errors first, with monitoring as a close neighbor when you validate releases. It is an integration layer, not a replacement for Sentry SDK setup or alert rules. Install when production noise is high and you want Claude Code or another MCP-capable agent to drill into Sentry as part of debug and iterate loops.

Highlights

  • MCP server exposing Sentry issues, errors, and search to LLM clients
  • Performance and trace exploration for cause analysis in chat
  • Stable and experimental tool surfaces documented in the bundle
  • AI-powered analysis keywords for monitoring and error tracking workflows
  • Two-plugin bundle from the official getsentry/sentry-mcp repository

Why builders use it

When production breaks, solo builders waste time flipping between the agent, Sentry’s web UI, and logs instead of having one conversational surface for errors and performance.

After registration, your agent can call Sentry MCP tools to fetch issues, errors, and trace context inside Claude Code, shortening root-cause loops during monitoring and fixes.

At a glance

  • Type - Plugin in DevOps.
  • Adoption - 0 installs, 623 stars, 0 votes.

FAQ

Who is getsentry-sentry-mcp for?

Developers shipping with Sentry who want LLM clients such as Claude Code to query monitoring data through the Model Context Protocol.

When should I use getsentry-sentry-mcp?

Use it during post-launch incident response, regression hunts, and performance investigations when conversational access to Sentry beats manual UI digging.

How do I add getsentry-sentry-mcp to my agent?

Install the getsentry/sentry-mcp Claude Code plugin, configure Sentry authentication per the MCP server docs, and enable the MCP tools in your Claude Code environment.

Discussion

Comments

Share how you use getsentry-sentry-mcp, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.