MCP server · Code and developer tools
Sentry MCP server
Lets a coding assistant search Sentry errors, traces and logs, triage issues and read Sentry docs while you debug.
- Maintainer
- Sentry (official)
- Licence
- FSL-1.1-ALv2
- Runs
- Remote (URL)
- Sign-in
- OAuth sign-in in the app
- Registry version
- 0.42.0 (updated 2026-09-25)
- Last activity
- 2026-10-14
Overview
What it does
Sentry MCP is Sentry’s hosted server at mcp.sentry.dev, built for coding agents that help with debugging. It sits in front of the Sentry API and signs you in with OAuth on first connection. You can scope the URL to one organisation or one project, which sets defaults and hides discovery tools; Sentry recommends project scoping where possible. The code now lives in the getsentry/toolkit repository alongside the Sentry CLI.
Use it when you want an assistant to look up the error behind a bug report, follow a trace or summarise an issue without opening the Sentry UI. Tools are grouped into skills such as inspect, triage, seer and project-management, and you can enable or disable skills to limit what is exposed. For self-hosted Sentry there is a stdio package, @sentry/mcp-server, which takes a user auth token and a --host flag. When you run it yourself, the natural-language search tools need a key for OpenAI, Azure OpenAI, Anthropic or OpenRouter; the other tools work without one.
Tools
What the assistant can do
- Search errors and issues in natural language
- Search traces and logs to analyse performance
- Triage issues (triage skill)
- Run Seer analysis on sentry.io (seer skill)
- Read Sentry documentation
- Manage projects and teams (project-management skill)
Install
Install Sentry MCP server in your app
You need:
- A Sentry account (sentry.io, or a self-hosted install via the stdio package)
- An MCP client with remote server and OAuth support
- For the stdio package: Node.js, a Sentry user auth token and, for AI search, an LLM provider API key
Run in your project. --scope local keeps the servers private to you in this project; use user for every project.
claude mcp add --scope local --transport http sentry https://mcp.sentry.dev/mcp
- sentry: if the server needs a sign-in, the app will ask (run /mcp in Claude Code).
Project root. Commit it to share the servers with your team; each person sets the variables in their own shell.
{
"mcpServers": {
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp"
}
}
}
- sentry: if the server needs a sign-in, the app will ask (run /mcp in Claude Code).
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json (Settings → Developer → Edit Config). Restart Claude after saving.
{
"mcpServers": {}
}
- sentry is a remote server: add it as a custom connector (Customize → Connectors → + Add → Add custom connector; on Team and Enterprise plans an owner adds it under Organization settings → Connectors), with the URL https://mcp.sentry.dev/mcp.
In your project, or ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
}
}
}
- sentry: if the server needs a sign-in, the app will ask.
In your workspace. VS Code asks for each secret the first time a server starts and stores it securely.
{
"servers": {
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp"
}
}
}
- sentry: if the server needs a sign-in, the app will ask.
macOS/Linux: ~/.config/devin/mcp_config.json · Windows: %APPDATA%\devin\mcp_config.json. Read by the default Devin Local agent and by the legacy Cascade agent.
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
}
}
}
- sentry: if the server needs a sign-in, the app will ask.
Want it alongside other servers? Open Sentry MCP in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.
Before you install
- Scope the URL to one organisation or project (https://mcp.sentry.dev/mcp/{organizationSlug}/{projectSlug}) so tools default to that data.
- The stdio token needs org:read, project:read, project:write, team:read, team:write and event:write, so it can change projects and teams. Turn off skills you do not need with --disable-skills or MCP_DISABLE_SKILLS (for example project-management).
- When self-run, AI-powered search sends your query text to the LLM provider you configure.
- A remote server sees whatever the assistant sends it. Sign in with the narrowest access the service offers. See how to choose a safe server.
Why it’s listed
Why we list it
Brings production error context into the editor from the vendor’s own hosted server, with org and project scoping and per-skill controls.
Related
More MCP servers
- GitHub MCP ServerLets an assistant read code, manage issues and pull requests, and check Actions runs in the GitHub repositories you can access.
- GitLab MCP serverGives an assistant access to GitLab projects, issues, merge requests, pipelines and search through an MCP endpoint built into GitLab.
- Figma MCP serverGives a coding assistant design context from Figma files, such as layout, variables and components, and can write back to the canvas.
- Semgrep MCP serverLets an assistant scan code for security issues with Semgrep, write custom rules and pull findings from Semgrep AppSec Platform.
- SonarQube MCP ServerConnects an assistant to SonarQube Cloud or Server to analyse code, review issues and hotspots, and check quality gates.
- Postman MCP ServerConnects an assistant to your Postman workspaces, collections, specs and environments, and can generate client code from APIs.
All MCP serversMCP config generatorGuide: MCP servers in Claude CodeGuide: what is MCP?