Sentry MCP Server
Official Sentry MCP server providing agent-native access to Sentry error tracking and performance monitoring. Enables agents to query issues, stack traces, releases, projects, and performance data directly from the MCP protocol without wrapping the REST API.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS enforced. API tokens have fine-grained scope controls. Tokens can be rotated in settings. MCP server runs locally, so credentials stay on the user's machine. SOC2 Type II certified. EU data residency available for GDPR compliance. Token exposure in MCP config files is a risk — use environment variables.
⚡ Reliability
Best When
An agent needs to investigate errors, understand crash patterns, or verify release health as part of a debugging or deployment workflow.
Avoid When
You need real-time log streaming, are using a monitoring platform other than Sentry, or need sub-second error alerting.
Use Cases
- • Fetch recent errors and full stack traces for debugging workflows
- • List performance regressions and N+1 query detections across releases
- • Check release health (crash-free sessions, error rates) before or after deployments
- • Triage and assign issues programmatically based on error patterns
- • Query projects and teams to understand organizational Sentry structure
Not For
- • Real-time log streaming (Sentry is event-based, not a log aggregator)
- • Non-Sentry monitoring backends (Datadog, New Relic, etc.)
- • High-frequency polling for live error feeds (use Sentry webhooks instead)
Interface
Authentication
MCP server uses Sentry API token authentication. Tokens are scoped (e.g., project:read, event:read, org:read). OAuth2 supported for user-delegated access. Tokens created in Sentry account settings with minimum required scopes.
Pricing
Free tier is genuinely useful for small projects. Paid tiers scale by event volume and data retention. Performance monitoring, profiling, and session replay are add-ons on some plans.
Agent Metadata
Known Gotchas
- ⚠ Organization slug is required for almost all queries — agents must know the org slug before making most requests
- ⚠ Issue vs event distinction matters: an Issue groups many Events; fetching an Issue gives aggregate data, fetching Events gives individual occurrences
- ⚠ Sentry query filter syntax is specific to Sentry (e.g., is:unresolved, assigned:me, has:commit) — not generic SQL
- ⚠ Data retention limits per plan affect historical queries — queries beyond retention window return empty results silently
- ⚠ MCP server requires running sentry-mcp as a local process or via npx — not a hosted cloud MCP endpoint
- ⚠ API token scopes must include the specific data types being queried — missing scopes return 403 without detail on which scope is needed
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Sentry MCP Server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.