Same collection group
Rootly MCP
Connect an assistant to Rootly incident response, on-call schedules, alerts, and incident analysis workflows.
MCPby getsentry · getsentry/toolkit
Sentry provides a hosted MCP endpoint for developer debugging workflows. Connect over HTTP and complete OAuth in a compatible client; self-hosted Sentry uses a separate local setup.
Sentry provides a hosted MCP endpoint for developer debugging workflows. Connect over HTTP and complete OAuth in a compatible client; self-hosted Sentry uses a separate local setup.
Illustrative saved transcript; historical tool calls and timings are not current API documentation or a live execution.
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
}
}
}claude mcp add --transport http sentry https://mcp.sentry.dev/mcpComplete the client OAuth flow on first connection. Optionally append /{organizationSlug}/{projectSlug} to scope the endpoint.
npx @sentry/mcp-server@latest --host=sentry.example.comSet SENTRY_ACCESS_TOKEN in the process environment. The official local setup lists org:read, project:read, project:write, team:read, team:write and event:write scopes; this is not a read-only token recipe. Select appropriate skills and follow the upstream setup for your deployment.
Client/version scope: Cursor / Claude Code HTTP. Other clients: pending verification.
Suggested prompts, not measured outcomes. Installation and listed tools were reviewed; these workflows were not executed.
Use sentry-mcp. Find the most-firing issue in project 'web' from the last 6 hours.
Get the latest event for that issue — stack trace, breadcrumbs, request data.
What release was running when this first appeared? List the commits in that release.
Looking at the stack and the commits — which commit likely caused this? Draft a fix in the relevant file.
Use sentry-mcp. Compare crash-free rate of release 1.4.0 vs 1.3.9 over their respective canary windows.
List any issues unique to 1.4.0 (not seen in 1.3.9 or earlier).
Given crash-free is X% and N net-new errors, recommend ship/halt with reason.
Use sentry-mcp. Get a trace for transaction 'POST /checkout' with duration > 2s from the last hour.
Compare span list to a similar trace from last week. Which spans are new or longer?
What commit added that query? Suggest an index or a query rewrite.
Integration compatibility: pending verification. Treat these as suggested workflows.
Pull issue X from Sentry, find the offending commit via GitHub, draft a fix as a new branch + PR.
For each new release-blocking issue in Sentry, create a Linear ticket with the stack + suggested owner.
Selected parameters checked against upstream definitions. Consult the connected server tools/list for your installed version.
issueUrl?: string, organizationSlug?: string, issueId?: string, eventId?: string, regionUrl?: string | null; provide an issue URL or identifying issue/event contextInspect a known issue; other tools depend on enabled skills
api_quota: pending verification
per_call_tokens: pending verification
monetary: pending verification: see current upstream pricing and hosting requirements.
budget_tip: Limit requested data and inspect actual output before expanding queries.
Hosted OAuth is managed by the client. Local stdio uses SENTRY_ACCESS_TOKEN.
Hosted requests pass through mcp.sentry.dev; self-hosted local setup uses the configured host.
Hosted: complete OAuth consent
Local stdio setup: org:read, project:read, project:write, team:read, team:write, event:write
Local documented scopes include writes; review enabled skills and consent.
CVE status and a full security audit: pending verification.
Check HTTP transport support and finish client OAuth. Use the separate local setup for self-hosted Sentry.
Pending verification: alternative projects and tradeoffs have not been rechecked.
Documentation checked 2026-10-08. No authenticated service was executed. Unchecked claims are marked pending verification.