Sentry
SentryPulls issues, stack traces, and event context into the agent so it can triage production errors with the actual payload in front of it
Pulls issues, stack traces, and event context into the agent so it can triage production errors with the actual payload in front of it On the other side: queries the datadog api for metrics, monitors, dashboards, and incident data
Sentry answers 'why did this break'; Datadog answers 'what is happening right now'.
Sentry is about the individual error: stack trace, breadcrumbs, which release introduced it. Datadog is about the system: metrics, monitors, and the shape of an incident. Teams often run both, and the agent should be pointed at whichever question it is actually asking.
| Option | Install | Source | Link |
|---|---|---|---|
| Sentry | hosted endpoint | Official | Repository ↗ |
| Datadog MCP | npx -y @winor30/mcp-server-datadog | Community | Repository ↗ |
An exception needs a cause — read the trace, the release, the affected users.
Something is slow or flapping and you need the series, not the stack.
A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.
Gives an agent scoped read, write, and search access to directories you explicitly allow
Read-only access to a repository's history: status, diffs, commit logs, and blame
Connects to Jira for issue lookup, JQL search, and comments
Reads content types and entries and can create drafts in a Contentful space
Searches Gmail and reads threads, with optional draft creation
Serves version-specific documentation for thousands of libraries, so an agent stops writing code against an API that changed two releases ago