Move from production error to a reviewable hypothesis.
Connect Sentry to d5s so agents can inspect errors, traces, releases, and project health during isolated incident investigations.
What agents can do with Sentry
Sentry provides the runtime evidence needed to understand what failed and who was affected. d5s exposes the connectable Sentry MCP method under a clean public brand, lets an agent investigate within policy, and records the chain from error to hypothesis without granting production authority.
- Inspect errors, traces, and affected releases
- Compare failure timing with deployment context
- Carry source links into the triage deliverable
Available connection methods
One public brand can have more than one verified access method. Pick the method that matches the workflow and credential policy.
Sign in with Sentry
MCP · oauth2
Connect Sentry's MCP server to investigate production issues in context.
Example compositions using Sentry
These examples show how the connector can participate in recurring work; they are patterns to build in d5s, not preinstalled workflow objects.
Morning operations brief
Review overnight incidents, group recurring signals, check the approved runbook, and deliver a source-linked morning handover.
Incident triage
Trace a production error, identify the likely change, and prepare a triage issue without giving the agent authority to modify production.
Try asking
Connect Sentry to a governed workflow.
Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.