a mcp server to get sentry issue by id or url for LLM
a mcp server to get sentry issue by id or url for LLM. That is what the sentry mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This is a mcp for sentry issue.\ It supports 2 tools to get a issue or list of issues.\ U can let LLM analysis the Res, or u want to do.
The server publishes 6 tools. What each one is for:
get_single_event — get a event detail infos, tiny mode return stack info, huge mode return all infoinputs — - url_or_id: sentry event url or sentry event idorganization_id_or_slug — sentry organization id or slug, it can be undefinedproject_id_or_slug — sentry project id or slug, it can be undefinedmode — tiny or huge, it can be undefinedget_project_events — get list of events, tiny mode return id and title, huge mode return all infoConfiguration is passed through the environment: SENTRY_HOST, SENTRY_ORG, SENTRY_PROJ, SENTRY_USER_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.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
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 — get_single_event, inputs, organization_id_or_slug and 3 more — is a fair guide to whether it matches your workflow. It is maintained by lee62; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_single_event | get a event detail infos, tiny mode return stack info, huge mode return all info |
| inputs | - url_or_id: sentry event url or sentry event id |
| organization_id_or_slug | sentry organization id or slug, it can be undefined |
| project_id_or_slug | sentry project id or slug, it can be undefined |
| mode | tiny or huge, it can be undefined |
| get_project_events | get list of events, tiny mode return id and title, huge mode return all info |
"mcpServers": {
"sentry-issue-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sentry-issues-mcp@latest"
],
"env": {
"SENTRY_HOST": "<your_sentry_host>",
"SENTRY_ORG": "<your_sentry_org>",
"SENTRY_PROJ": "<your_sentry_proj>",
"SENTRY_USER_TOKEN": "<your_sentry_user_token>"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SENTRY_HOST | Endpoint or connection string the server talks to. | Optional |
| SENTRY_ORG | Configuration value read at startup. | Optional |
| SENTRY_PROJ | Configuration value read at startup. | Optional |
| SENTRY_USER_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.