{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/",
    "json": "https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 6 | 10 | 12 | 6 |\n\n## What counts as done\n\nThe 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.\n\nHow agents ask for it: 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\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Better Stack (Better Stack, Inc.)**: 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.\n- **Cronitor MCP server (Cronitor)**: 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.\n- **Grafana MCP Server (Raintank Inc., d/b/a Grafana Labs)**: 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.\n- **incident.io API (Pineapple Technology Ltd.)**: 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.\n- **PagerDuty MCP Server (PagerDuty, Inc.)**: 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.\n- **Rootly MCP Server (Rootly Inc.)**: 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.\n\n- not this job: Axiom MCP Server (Axiom, Inc.): Monitors and their alert history only; no incident, timeline, schedule or override tools.\n- not this job: Causely MCP server (Causely, Inc.): No on-call schedules, and Issues are inferred diagnoses rather than incident records; the only write is snoozing an Issue.\n- not this job: Datadog MCP Server (Datadog, Inc.): 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.\n- not this job: Honeycomb MCP (Hound Technology, Inc. d/b/a Honeycomb): No incident, timeline or on-call tools.\n- not this job: New Relic MCP Server (New Relic, Inc.): Alert events and issues are readable, but there are no incident writes, notes or on-call tools; the server is read-only.\n- not this job: Sentry MCP (Functional Software, Inc. d/b/a Sentry): No incident records or on-call schedules; issues are errors, not incidents.\n\n## What stops agents finishing\n\n- API or MCP gated to a paid tier (PagerDuty Professional, incident.io Team)\n- write tool assigns a person without asking them\n- duplicate incident or page after a retried create\n\n## Around it\n\nBefore: observability.investigate-alert, calendar.read-events. After: messaging.post-summary, notifications.page.\n\n## Where this comes from\n\nWeight 12 of 100 in Observability \u0026 incidents: 6 of 42 accounts, four of them GitHub issues on PagerDuty and Rootly servers; incident.io named in two\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/observability.oncall-and-incident-records.json, or the MCP tool get_use_case with id observability.oncall-and-incident-records. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "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"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Read and update incidents and on-call",
        "url": ""
      }
    ],
    "description": "Read and update incidents and on-call: 0 companies fully do it, 6 with a limit, 10 carry the tag. Every listing in Observability \u0026 incidents with the reason and a source.",
    "facts": null,
    "h1": "Read and update incidents and on-call",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/observability.oncall-and-incident-records/",
    "published": "",
    "section": "agents",
    "title": "Read and update incidents and on-call: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/"
  },
  "tokens": {
    "markdown": 1200,
    "slim": 280
  },
  "version": 1
}
