# Instatus — MCP server on mcp.ai
> Connect your Instatus account and use 15 tools for server monitoring straight from your AI agent. Connect with your own API key. Instatus is a status page and incident communication platform for managing service health, incidents, maintenance, monitors, and subscribers.

By: mcp.ai · official
Page: https://mcp.ai/instatus

## Connect (MCP protocol)
Remote MCP endpoint (HTTP, streamable): https://api.mcp.ai/p_instatus?ms=1787296080000
Add it as a custom/remote MCP connector, then authenticate when prompted.

## REST API (no MCP client required)
Every tool is also a REST endpoint, authed with a workspace API key.
Discover: GET https://api.mcp.ai/api/instatus/_endpoints   # public; lists every endpoint
Call:     POST https://api.mcp.ai/api/instatus/<endpoint>
  Authorization: Bearer sk_live_…   # create one at https://mcp.ai/settings/api-keys
  Content-Type: application/json
  Body: { …args }   →   { "ok": true, "tool": "<id>", "result": { … } }

## Developer docs
How to use (MCP or REST), markdown: https://mcp.ai/instatus/skill.md
Postman collection (v2.1): https://mcp.ai/instatus/postman.json

## Tools
- instatus_add_incident_update(notify?: boolean, status: string, message?: string, page_id: string, started_at?: string, incident_id: string, component_ids: string[], component_statuses: object[]) — Post a public lifecycle update to an Instatus incident and change affected component states. This can send external notifications to page and affected-component subscribers when notify is true.
- instatus_add_maintenance_update(end_at?: string, notify?: boolean, status?: string, message?: string, page_id: string, started_at: string, component_ids?: string[], maintenance_id: string, component_statuses?: object[]) — Post a public progress update to an Instatus maintenance, optionally changing its lifecycle, timing, and affected component states. This can send external notifications to page and affected-component 
- instatus_create_component(name: string, order?: integer, status?: string, grouped?: boolean, page_id: string, group_id?: string, description?: string, show_uptime?: boolean) — Create a component on an Instatus status page. This changes the page's component configuration and can make the new component and its initial health status publicly visible.
- instatus_create_incident(name: string, notify?: boolean, status: string, message?: string, page_id: string, started_at?: string, component_ids?: string[], should_publish?: boolean, component_statuses?: object[]) — Create an incident on an Instatus status page with optional affected component states. The incident is published publicly by default; notify=true can send notifications to page and affected-component 
- instatus_create_maintenance(name: string, end_at: string, notify: boolean, status: string, message?: string, page_id: string, auto_end: boolean, start_at: string, expand_at?: string, auto_start: boolean, notify_end: boolean, is_collapsed?: boolean, notify_early: boolean, notify_start: boolean, component_ids: string[], notify_minutes?: integer, duration_minutes?: integer, component_statuses?: object[]) — Schedule or start a maintenance on an Instatus status page. The required notification controls are side-effecting: notify can contact subscribers immediately, while notify_start, notify_end, and notif
- instatus_get_component(page_id: string, component_id: string) — Get the current health and configuration of one component on an Instatus status page.
- instatus_get_incident(page_id: string, incident_id: string) — Get one Instatus incident with its affected components and update history.
- instatus_get_maintenance(page_id: string, maintenance_id: string) — Get one Instatus maintenance with its schedule, affected components, automation settings, and update history.
- instatus_list_components(page_id: string, per_page?: integer, next_cursor?: string) — List components and their current health for one Instatus status page, including child components where present. Pass the response's next_cursor back unchanged to fetch another page.
- instatus_list_incidents(page_id: string, per_page?: integer, next_cursor?: string, exclude_statuses?: string, include_statuses?: string) — List incidents for an Instatus status page, optionally including or excluding lifecycle statuses.
- instatus_list_maintenances(page_id: string, per_page?: integer, next_cursor?: string) — List scheduled and historical maintenances for an Instatus status page.
- instatus_list_status_pages(per_page?: integer, next_cursor?: string) — List status pages available to the connected Instatus account so an agent can discover page IDs for component, incident, and maintenance operations.
- instatus_update_component(name?: string, order?: integer, status?: string, grouped?: boolean, page_id: string, description?: string, show_uptime?: boolean, component_id: string) — Change a component's health or presentation on an Instatus status page.
- instatus_update_incident(name?: string, notify?: boolean, status?: string, page_id: string, started_at: string, incident_id: string, component_ids?: string[], component_statuses?: object[]) — Edit an existing Instatus incident's name, timing, lifecycle status, affected components, or component states. Setting notify to true sends notifications to page and affected-component subscribers.
- instatus_update_maintenance(name?: string, end_at: string, notify: boolean, status: string, message: string, page_id: string, auto_end: boolean, start_at: string, auto_start: boolean, component_ids: string[], maintenance_id: string, duration_minutes: integer, component_statuses: object[]) — Fully replace an Instatus maintenance's public message, schedule, lifecycle state, affected components and states, and automation settings. Call INSTATUS_GET_MAINTENANCE first and preserve unchanged v

## Example prompts
- "What can I do in Instatus?"
- "Show me a summary of my Instatus account"

## Links
Docs: https://mcp.ai/docs/mcps/instatus
Website: https://mcp.ai/mcps/instatus