list_projectsLABSCO 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.
Setup effort
Build from source
USE CASES
01
Following up on an issue reference someone pasted in chat
Resolve the short ID, then pull the specific event to see what actually failed.
02
Finding out what is currently broken in a service
List the project's issues, then the error events inside the one that matters.
03
Working out which project a team's errors live in
List the organization's projects in detail before going any further.
04
Getting the output into a document rather than a terminal
Ask for Markdown instead of plain text per call, so the answer pastes cleanly into an incident write-up.
05
Standing up somewhere for a new service's errors to go
Create the project from the conversation instead of switching to the Sentry UI.
9 tools
Listed in project docs. Your client may show a different list.
resolve_short_idget_sentry_eventlist_error_events_in_projectcreate_projectlist_project_issueslist_issue_eventsget_sentry_issuelist_organization_replaysBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
- Node.js
- SENTRY_AUTH in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
Clone the repository and install its dependencies: git clone https://github.com/getsentry/sentry-mcp-stdio.git, then cd sentry-mcp-stdio and npm install
Create a Sentry auth token under Settings → User Settings → Auth Tokens
Add this to your Claude settings, with the path to index.ts in your clone and your token:
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"sentry": {
"command": "npx",
"args": [
"ts-node",
"/Users/<YOUR_USERNAME>/sentry-mcp-stdio/index.ts"
],
"env": {
"SENTRY_AUTH": "<YOUR_AUTH_TOKEN>"
}
}
}
}
