How to add Sentry MCP
Connect Sentry through its named card in Durin and verify an allowed read and a denied write before rollout.
Prepare Sentry access
Use the named Sentry card with https://mcp.sentry.dev/mcp. Durin registers its own OAuth client with Sentry, so no client ID or secret is needed. Sentry consent chooses the skills; updating issues requires Triage. The grant is not limited to one organization.
Save, review and enable
Open Admin → Connections → All providers and choose Sentry. Keep Register automatically and leave OAuth scopes blank. Save the draft, sign in, discover tools, save permission review and obtain the matching deployed validator. Run an approved read test, review billing, confirm activation and enable the reviewed tools.
Review execute_sentry_tool and analyze_issue_with_seer as writes: the first runs other Sentry tools your skills allow, including deletes and project administration; the second starts a paid Seer analysis. The card is not limited to one Sentry project.
Complete personal provider access, copy your Durin connection URL and authenticate your MCP client for that exact URL.
Read and snooze a test issue
In a dedicated test project, read one unresolved issue with get_sentry_resource, using resourceType issue and its short ID. Snooze it once with update_issue: status ignored, ignoreMode forDuration, ignoreDurationMinutes 30. Omit reason, which Sentry posts as a comment.
- Expected success: the issue details, then one snooze that Sentry lifts after 30 minutes; activity records both executions.
- Expected denial: configure Durin to deny writes and repeat the snooze; update_issue leaves discovery and no new provider dispatch occurs. Reads continue.
Troubleshooting
Sign-in succeeds but a tool is unavailable
Check the skills granted at Sentry consent, personal consent, team access, permitted resources, deployed validator and activation. Discovery and an approved request alone do not grant access.
Frequently asked questions
What should I record?
Record client, version, UTC date, tool/schema revision and both activity IDs when you complete the workflow.