# Read and update incidents and on-call

> Read and update incidents and on-call: 0 companies fully do it, 6 with a limit, 10 carry the tag. Every listing in Observability & incidents with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/
- Markdown: https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/observability.oncall-and-incident-records/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 6 | 10 | 12 | 6 |

## What counts as done

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.

How 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

## Does the job, with a limit

It 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.

- **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.
- **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.
- **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.
- **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.
- **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.
- **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.

- not this job: Axiom MCP Server (Axiom, Inc.): Monitors and their alert history only; no incident, timeline, schedule or override tools.
- 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.
- 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.
- not this job: Honeycomb MCP (Hound Technology, Inc. d/b/a Honeycomb): No incident, timeline or on-call tools.
- 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.
- not this job: Sentry MCP (Functional Software, Inc. d/b/a Sentry): No incident records or on-call schedules; issues are errors, not incidents.

## What stops agents finishing

- 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

## Around it

Before: observability.investigate-alert, calendar.read-events. After: messaging.post-summary, notifications.page.

## Where this comes from

Weight 12 of 100 in Observability & incidents: 6 of 42 accounts, four of them GitHub issues on PagerDuty and Rootly servers; incident.io named in two

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
