create_status_page_incident

sh.fettle/mcp · Verify this server

Open an incident on a status page with a first message. This is public and emails the page's confirmed subscribers (details below): confirm the wording with the user before calling. Requires a key with the write scope. page_id (uuid, required) is the page's id from list_status_pages; an id that is not a status page of this organization is a 404. Required: title (1 to 255 characters) and body (the first message, 1 to 5000 characters). status is INVESTIGATING, IDENTIFIED, MONITORING or RESOLVED; RESOLVED closes the incident on the page. It defaults to INVESTIGATING. Any status but RESOLVED emails every confirmed subscriber of the page at once; RESOLVED records an already closed incident (a postmortem) and emails nobody. component_ids (optional array of component uuids from get_status_page) marks the affected components; an id that is not a component of this page is a 404. Returns the incident. Example: {"page_id": "<id from list_status_pages>", "title": "API errors", "body": "We are investigating elevated error rates."}