# Best observability and incident tools for AI agents (slim)

> Grafana MCP Server (BB), Sentry MCP (BB) and incident.io API (B) lead the 7 ranked observability and incident tools. Picks by need, strengths, weaknesses and prices from the Anchor benchmark.

- Full: https://www.anchorterminal.com/best/observability/index.md (~4,500 tokens) · this version ~1,180 tokens · JSON https://www.anchorterminal.com/best/observability/index.json · canonical https://www.anchorterminal.com/best/observability/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09

All 7 ranked observability and incident tools on the Anchor benchmark, with a pick for each need and where each one falls short. Scores come from public evidence, re-checked as vendors change.

- Ranked: 7 · agent-ready (BB or better): 2 · accept x402: 0 · hosted endpoints: 6
- Full ranked table: https://www.anchorterminal.com/categories/observability.md
- Head-to-head comparisons: https://www.anchorterminal.com/compare/observability/index.md (15)
- Methodology: https://www.anchorterminal.com/benchmark/index.md

## The shortlist

| # | Tool | Grade | Score | Best for | Price | Where |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | [Grafana MCP Server](https://www.anchorterminal.com/tools/grafana-mcp-server.md) | BB | 74.5 | Teams on Grafana, self-managed or Cloud, that want an agent to read dashboards and query Prometheus, Loki, Tempo and Pyroscope, and to work with alert rules, incidents and OnCall. | Free · OSS | local |
| 2 | [Sentry MCP](https://www.anchorterminal.com/tools/sentry-mcp.md) | BB | 70.2 | Coding agents that triage and fix production errors from Sentry. datadog-mcp covers wider observability data, pagerduty-mcp on-call and incidents. | Your plan | hosted and local |
| 3 | [incident.io API](https://www.anchorterminal.com/tools/incident-io.md) | B | 68.9 | Agents that declare and update incidents, page people, read on-call schedules and post status page incidents in an organisation that already pays for incident.io. | $19 / seat-mo | hosted |
| 4 | [Rootly MCP Server](https://www.anchorterminal.com/tools/rootly-mcp.md) | C | 59.7 | Incident and on-call agents in teams that already run Rootly. | $20 / seat-mo | hosted and local |
| 5 | [Honeycomb MCP](https://www.anchorterminal.com/tools/honeycomb-mcp.md) | C | 58.3 | Agents that investigate latency and error spikes in a team already sending traces and events to Honeycomb, and that record findings as Boards, Triggers or SLOs. | Your plan | hosted |
| 6 | [Datadog MCP Server](https://www.anchorterminal.com/tools/datadog-mcp.md) | C | 56.6 | Agents that triage production issues across metrics, logs, traces and monitors in a Datadog org. sentry-mcp is narrower and deeper on errors, pagerduty-mcp covers on-call. | Your plan | hosted and local |
| 7 | [PagerDuty MCP Server](https://www.anchorterminal.com/tools/pagerduty-mcp.md) | D | 48.4 | Incident and on-call agents in PagerDuty shops. | Your plan | hosted |

## Picks by need

- Highest score overall: [Grafana MCP Server](https://www.anchorterminal.com/tools/grafana-mcp-server.md), BB, 74.5/100 on the benchmark. Also [Sentry MCP](https://www.anchorterminal.com/tools/sentry-mcp.md), BB, 70.2/100.
- Schema & documentation: [incident.io API](https://www.anchorterminal.com/tools/incident-io.md), 88/100 on schema & documentation, against 81 for the overall leader.
- Agent ergonomics: [Sentry MCP](https://www.anchorterminal.com/tools/sentry-mcp.md), 85/100 on agent ergonomics, against 74 for the overall leader.
- Security & auth: [Datadog MCP Server](https://www.anchorterminal.com/tools/datadog-mcp.md), 76/100 on security & auth, against 65 for the overall leader.
- Transparency & trust: [Sentry MCP](https://www.anchorterminal.com/tools/sentry-mcp.md), 81/100 on transparency & trust, against 79 for the overall leader.
- A hosted MCP endpoint: [Sentry MCP](https://www.anchorterminal.com/tools/sentry-mcp.md), remote MCP server, nothing to install.

## How to choose

- Signal coverage and on-call data: Check which of errors, metrics, logs, traces and on-call data the tool exposes, since an agent debugging an incident can only reason over the signals it can query.
- Idempotency of incident writes: Check whether incident and on-call writes are idempotent, because an agent that retries after a timeout could otherwise open duplicate incidents or page the same person twice.
- Limits on large time ranges: Check the rate limits and pagination on log and metric queries, since an agent scanning a long time range can hit a limit and miss data.
- Freshness of returned state: Check how current returned metrics and incident states are and whether responses report the time they were last changed, so an agent does not reason from stale state.

Each listing's verdict, strengths and weaknesses: https://www.anchorterminal.com/best/observability/index.md