sentry-issues-mcp

Sentry Issues MCP Server

Sentry issue investigation connects to LLM workflows through sentry-issues-mcp. Developers can retrieve an individual issue event or project events, then ask an LLM to examine the returned information for possible causes and fixes.

Server facts

sentry-issues-mcp

Project

Author
Leee62
License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
5
Last commit
Data as of

Tags

  • Sentry
  • issue
  • llm
  • mcp

Overview

Sentry errors provide the starting point for sentry-issues-mcp, which exposes retrieval tools for developers investigating project problems with an LLM. The listed get_single_event tool accepts a Sentry issue event URL or event ID to retrieve an individual event. For a broader view, get_project_events retrieves issue events using organization and project identifiers. These retrieval paths support moving from a specific error reference to project-level information without making the language model itself the source of the Sentry records.

The documented workflows pair retrieval with requests for interpretation: examine a referenced issue, discuss its cause, and suggest how it might be fixed. Another example asks the LLM to identify the most dangerous issue for the day and explain it. Those are analysis requests made to the LLM, rather than separate diagnostic tools. Connection configuration uses stdio and environment fields for the Sentry host, organization, project, and user token. The README also describes organization identifiers as optional inputs for its issue-fetching tools.

sentry-issues-mcp setup notes

  • sentry-issues-mcp records stdio only; confirm a network transport upstream before planning remote access.
  • sentry-issues-mcp has no recorded license; confirm reuse terms in its repository.

Related MCP servers