Sentry MCP Server
MCP server for exposing Sentry errors, issues, and observability context to coding assistants.
Host support
Source boundary
The Sentry MCP repository describes an MCP server for interacting with Sentry through LLM assistants.
Sources
| Source | Type | Verified | Citation |
|---|---|---|---|
| Sentry MCP GitHub | github | 2026-09-15 | Public Sentry repository for the MCP server. |
Relationships
| Type | Source | Target | Citation |
|---|---|---|---|
| supports | sentry-mcp-server | observability-context | Sentry MCP repository positions the server around Sentry issue and observability context. |
Compatibility
| Type | Target | Status | Evidence |
|---|---|---|---|
| server_host | claude-code | verify_required | Sentry MCP Server may be configured for Claude Code MCP workflows, but server command, authentication, and workspace permissions must be checked locally. |
| server_host | visual-studio-code | verify_required | Sentry MCP Server can be considered for VS Code MCP-compatible workflows, but extension-level MCP support, authentication, and transport configuration must be verified. |
What makes an agent stack enterprise-ready?
An enterprise-ready stack should expose governance boundaries, source verification, observability, host compatibility, and deployment paths that match existing platform and language constraints.
Should debugging agents start from Sentry MCP Server or GitHub MCP Server?
Start from Sentry MCP Server when the task begins with runtime errors or incidents. Start from GitHub MCP Server when repository, issue, pull request, or code review context is the primary source of truth.