A Model Context Protocol (MCP) server for Sentry
MCP Sentry Ts MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A 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.
Once MCP Sentry Ts is connected, these are the calls the assistant has available:
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 serverts-node on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: SENTRY_AUTH, YOUR_AUTH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Sentry Ts'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 codyde; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| 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-ts": {
"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.