{
  "listings": [
    {
      "slug": "better-stack",
      "name": "Better Stack",
      "company": "Better Stack, Inc.",
      "grade": "C",
      "fit": "caveat",
      "why": "Incident details, timeline and comments are separate read tools and on-call reads exist, but create incident takes no idempotency key and there is no override or coverage-request tool.",
      "source": "https://betterstack.com/docs/getting-started/integrations/mcp/",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/better-stack"
    },
    {
      "slug": "cronitor-mcp",
      "name": "Cronitor MCP server",
      "company": "Cronitor",
      "grade": "C",
      "fit": "caveat",
      "why": "Issues read with update history and are created, updated and resolved by tool; updates carry keys to avoid duplicate history, but create_issue has no stated dedup key and there is no on-call schedule.",
      "source": "https://cronitor.io/docs/mcp-server",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/cronitor-mcp"
    },
    {
      "slug": "grafana-mcp-server",
      "name": "Grafana MCP Server",
      "company": "Raintank Inc., d/b/a Grafana Labs",
      "grade": "BB",
      "fit": "caveat",
      "why": "get_incident, add_activity_to_incident and OnCall schedule, shift and current-user reads exist, but no override or coverage write, and the README shows no idempotency key on create_incident.",
      "source": "https://github.com/grafana/mcp-grafana",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/grafana-mcp-server"
    },
    {
      "slug": "incident-io",
      "name": "incident.io API",
      "company": "Pineapple Technology Ltd.",
      "grade": "B",
      "fit": "caveat",
      "why": "incident_show and incident_update_list give body and history; schedule_override_create and cover_request_create cover on-call; the REST API takes idempotency_key on incidents and escalations. MCP and API need Team or above, a blocker the map names.",
      "source": "https://docs.incident.io/ai/remote-mcp.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/incident-io"
    },
    {
      "slug": "pagerduty-mcp",
      "name": "PagerDuty MCP Server",
      "company": "PagerDuty, Inc.",
      "grade": "E",
      "fit": "caveat",
      "why": "browse_incidents gets incidents, alerts and notes, manage_incidents adds notes and responders, manage_schedules creates overrides; but the body is missing without include[]=body (#65, open), no idempotency key is documented, and MCP needs Professional or above.",
      "source": "https://docs.pagerduty.com/ai-automation/advance/pagerduty-mcp-server.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/pagerduty-mcp"
    },
    {
      "slug": "rootly-mcp",
      "name": "Rootly MCP Server",
      "company": "Rootly Inc.",
      "grade": "C",
      "fit": "caveat",
      "why": "Incident and shift tools exist and create_override_shift writes overrides, but there is no coverage-request tool (#338, open, where the only write assigns someone without asking) and no idempotency key is documented. Essentials plan or above.",
      "source": "https://github.com/rootlyhq/rootly-mcp-server",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/rootly-mcp"
    },
    {
      "slug": "axiom",
      "name": "Axiom MCP Server",
      "company": "Axiom, Inc.",
      "grade": "BB",
      "fit": "no",
      "why": "Monitors and their alert history only; no incident, timeline, schedule or override tools.",
      "source": "https://axiom.co/docs/console/intelligence/mcp-server/tools",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/axiom"
    },
    {
      "slug": "causely",
      "name": "Causely MCP server",
      "company": "Causely, Inc.",
      "grade": "E",
      "fit": "no",
      "why": "No on-call schedules, and Issues are inferred diagnoses rather than incident records; the only write is snoozing an Issue.",
      "source": "https://docs.causely.ai/agent-integration/mcp-server/",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/causely"
    },
    {
      "slug": "datadog-mcp",
      "name": "Datadog MCP Server",
      "company": "Datadog, Inc.",
      "grade": "D",
      "fit": "no",
      "why": "get_datadog_incident is documented as not including timeline data, no tool declares an incident or adds a note, and there are no on-call tools.",
      "source": "https://docs.datadoghq.com/bits_ai/mcp_server/tools/",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/datadog-mcp"
    },
    {
      "slug": "honeycomb-mcp",
      "name": "Honeycomb MCP",
      "company": "Hound Technology, Inc. d/b/a Honeycomb",
      "grade": "B",
      "fit": "no",
      "why": "No incident, timeline or on-call tools.",
      "source": "https://docs.honeycomb.io/integrations/mcp/tools",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/honeycomb-mcp"
    },
    {
      "slug": "new-relic",
      "name": "New Relic MCP Server",
      "company": "New Relic, Inc.",
      "grade": "B",
      "fit": "no",
      "why": "Alert events and issues are readable, but there are no incident writes, notes or on-call tools; the server is read-only.",
      "source": "https://docs.newrelic.com/docs/agentic-ai/mcp/tool-reference/",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/new-relic"
    },
    {
      "slug": "sentry-mcp",
      "name": "Sentry MCP",
      "company": "Functional Software, Inc. d/b/a Sentry",
      "grade": "B",
      "fit": "no",
      "why": "No incident records or on-call schedules; issues are errors, not incidents.",
      "source": "https://github.com/getsentry/sentry-mcp/tree/main/packages/mcp-core/src/tools/catalog",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/sentry-mcp"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "useCase": {
    "accounts": 6,
    "after": [
      "messaging.post-summary",
      "notifications.page"
    ],
    "area": "developer",
    "asks": [
      "who is on call for payments",
      "open an incident for this",
      "add a timeline note",
      "find a cover for my shift next week",
      "get the alert body for this incident"
    ],
    "before": [
      "observability.investigate-alert",
      "calendar.read-events"
    ],
    "blockers": [
      "API or MCP gated to a paid tier (PagerDuty Professional, incident.io Team)",
      "write tool assigns a person without asking them",
      "duplicate incident or page after a retried create"
    ],
    "capabilities": [
      "observability.incidents",
      "work.oncall"
    ],
    "category": "observability",
    "categoryName": "Observability \u0026 incidents",
    "checked": "2026-11-15",
    "companies": {
      "fit": 0,
      "fitWithLimit": 6,
      "tagged": 10
    },
    "competition": "none",
    "fits": null,
    "fitsWithLimit": [
      "better-stack",
      "cronitor-mcp",
      "grafana-mcp-server",
      "incident-io",
      "pagerduty-mcp",
      "rootly-mcp"
    ],
    "id": "observability.oncall-and-incident-records",
    "listings": {
      "caveat": 6,
      "no": 6,
      "notRead": 0,
      "tagged": 10,
      "unchecked": 0,
      "yes": 0
    },
    "name": "Read and update incidents and on-call",
    "status": "draft",
    "success": "The incident or schedule read with its body, alerts and timeline; any write (declare, note, override, coverage request) applied once even if retried, and the change visible on a re-read.",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/observability.oncall-and-incident-records.json",
    "weight": 12,
    "weightBasis": "6 of 42 accounts, four of them GitHub issues on PagerDuty and Rootly servers; incident.io named in two"
  }
}
