Model Context Protocol (MCP) server for Sentry
If you already use Sentry, the sentry mcp server is the piece that lets your assistant work with it directly. Model Context Protocol (MCP) server for Sentry.
A Model Context Protocol (MCP) server for interacting with Sentry. This MCP server provides tools to interact with the Sentry API, allowing AI assistants to retrieve and analyze error data, manage projects, and monitor application performance.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_projects — Lists all accessible Sentry projects for a given organizationresolve_short_id — The resolve_short_id tool exposed by this serverget_sentry_event — Retrieves and analyzes a specific Sentry event from an issuelist_error_events_in_project — The list_error_events_in_project tool exposed by this servercreate_project — Creates a new project in Sentry and retrieves its client keyslist_project_issues — The list_project_issues tool exposed by this serverlist_issue_events — The list_issue_events tool exposed by this serverget_sentry_issue — The get_sentry_issue tool exposed by this serverlist_organization_replays — The list_organization_replays tool exposed by this serverConfiguration is passed through the environment: SENTRY_AUTH, YOUR_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Sentry's toolset — list_projects, resolve_short_id, get_sentry_event and 6 more — is a fair guide to whether it matches your workflow. It is maintained by getsentry; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Sentry's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_projects | Lists all accessible Sentry projects for a given organization. |
| resolve_short_id | The resolve_short_id tool exposed by this server. |
| get_sentry_event | Retrieves and analyzes a specific Sentry event from an issue. |
| list_error_events_in_project | The list_error_events_in_project tool exposed by this server. |
| create_project | Creates a new project in Sentry and retrieves its client keys. |
| list_project_issues | The list_project_issues tool exposed by this server. |
| list_issue_events | The list_issue_events tool exposed by this server. |
| get_sentry_issue | The get_sentry_issue tool exposed by this server. |
| list_organization_replays | The list_organization_replays tool exposed by this server. |
{
"mcpServers": {
"sentry-mcp-stdio": {
"command": "npx",
"args": ["-y", "ts-node"],
"env": {
"SENTRY_AUTH": "your-value",
"YOUR_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SENTRY_AUTH | Configuration value read at startup. | Optional |
| YOUR_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.