get_incident
Get Incident
Retrieve detailed information about a specific incident including its full update history, affected components, and current status.
Ask your agent in plain language. Each of these maps to a real tool on the server.
get_incident
Retrieve detailed information about a specific incident including its full update history, affected components, and current status.
create_incident
Create a new incident on the status page. Supports realtime, scheduled, and backfilled (historical) incident types. - **Realtime**: Set `status` to investigating/identified/monitoring/resolved. Notifications are sent to subscribers. - **Scheduled**: Provide `scheduledFor` and `scheduledUntil` for planned maintenance. - **Historical**: Set `backfilled` to true and provide `backfillDate` for past incidents. Optionally associate affected components and their statuses.
manage_subscriber
Create, inspect, or unsubscribe a subscriber on the status page. - To **create**: provide the subscriber `type` and the relevant contact info (email, phone, webhookEndpoint, etc.). Optionally scope to specific components. - To **unsubscribe**: provide `subscriberId` and set `unsubscribe` to true. - To **inspect**: provide `subscriberId` without an action flag. The legacy resubscribe flag is unsupported by the current API. Creation and unsubscription can notify the contact. Confirmation suppression applies only to paid pages; trial pages still send confirmations.
manage_component_group
Create, update, or delete component groups on the status page. Component groups organize related components together. - To **create**: omit `groupId` and provide `name` and optionally `componentIds`. - To **update**: provide `groupId` and the fields to change. - To **delete**: provide `groupId` and set `delete` to true. - To **list**: omit all fields to list all component groups.
get_page
Retrieve the status page profile and settings including name, domain, subdomain, time zone and notification preferences. Use this to inspect current page configuration.
manage_postmortem
Create, update, publish, or revert a postmortem for a resolved incident. Postmortems support a draft workflow: - **Get**: Retrieve the current postmortem for an incident. - **Save draft**: Provide `body` to create or update the postmortem draft. - **Publish**: Set `publish` to true with optional subscriber/Twitter notifications. - **Revert**: Set `revert` to true to revert a published postmortem back to draft.
list_incident_templates
List a page of incident templates configured for the status page. Templates contain pre-filled incident names, messages, statuses, and component associations for quick incident creation.
list_incidents
List incidents on the status page with optional filtering. Can retrieve all incidents, only unresolved, only scheduled, or search by keyword.
update_page
Update status page profile settings such as name, domain, subdomain, time zone and subscriber notification preferences. Changes affect the live status page and subscription options.
manage_component
Create, update, or delete a component on the status page. Components represent infrastructure pieces like APIs, apps, and services. - To **create**: omit `componentId` and provide `name` at minimum. - To **update**: provide `componentId` and the fields to change (e.g. `status`, `name`, `description`). - To **delete**: provide `componentId` and set `delete` to `true`.
submit_metric_data
Submit custom metric data points to a metric on the status page. Data points are timestamp/value pairs displayed as performance charts. Data should be submitted at least every 5 minutes for continuous display. Can backfill up to 28 days.
update_incident
Update an existing incident's status, message, impact, or associated components. Each update creates a new entry in the incident timeline. Use this to progress an incident through its lifecycle (investigating -> identified -> monitoring -> resolved) or to delete it.
list_subscribers
List subscribers on the status page with optional filtering by type and state. Returns subscriber contact information and subscription scope.
list_components
List a page of components on the status page. Returns each component's name, status, group, and configuration. Use this to get an overview of all infrastructure pieces being tracked.
manage_metric
Discover metric providers, list or inspect system metrics, and create, rename or delete a metric. A metric provider must already exist; list_providers discovers its ID. Creation can display a chart on the status page unless display=false. Use submit_metric_data to send custom data to a Self provider metric.
list_pages
Discover status pages accessible to the API key, including IDs for page-scoped operations. This lists accessible pages, not the identity of an account user.
Every client uses the same Magic MCP URL, and so does any other MCP client. Add it once and sign in with SSO.
{"mcpServers": {"metorial": {"url": "<your-magic-mcp-url>"}}}
claude mcp add --transport http metorial <your-magic-mcp-url>
codex mcp add metorial --url <your-magic-mcp-url>codex mcp login metorial
One governed layer for every app your agents reach, not a separate connector per tool.
Manage status pages to communicate incidents, outages, and scheduled maintenance to customers. Create, update, and resolve incidents with lifecycle tracking. Manage components representing infrastructure pieces and their statuses (operational, degraded, partial/major outage). Create and publish incident postmortems. Configure scheduled maintenance with subscriber reminders and auto-transitions. Manage subscribers (email, SMS, Slack, webhook, Teams) scoped to pages, components, or incidents. Submit and display custom system performance metrics. Create reusable incident templates for faster response. Control page access with user groups and role-based permissions. Configure embeddable status widgets.
Common questions about connecting Statuspage to AI agents with Metorial.