Labsco
MCP SERVER · OFFICIAL PROJECT

Sentry MCP Server

by getsentry

Read Sentry issues and events from the chat — turn a short ID like PROJECT-123 into the stack behind it.

Observability, Monitoring & Incident ResponseOfficial source
Summary
The short-ID lookup is the reason to keep it around.

Someone pastes PROJECT-123 into a thread and resolve_short_id turns it into the issue and its events without anyone opening Sentry. Sentry's own README points at their hosted server as the fuller option and keeps this one as a standalone example — so choose it when you want a local server and a token you control.

What it is

A standalone TypeScript server over the Sentry API, run locally with an auth token. Sentry also runs a hosted server at mcp.sentry.dev with more capability; this is the self-contained one you host yourself.

What you get
  • list_projects for every project in an organization, as a summary or in detail
  • resolve_short_id to turn a reference like PROJECT-123 into the issue behind it
  • get_sentry_event for one event inside an issue, taking either the full issue URL or the numeric ID
  • list_project_issues and list_error_events_in_project to work through a project
  • create_project
  • Output as plain text or Markdown, chosen per call
Requirements

Node 14 or newer, npm or yarn, and a Sentry account with API access. A Sentry auth token with the right permissions goes into the server's environment; the server is launched with npx ts-node against a local checkout.