openstatus MCP server
The openstatus MCP server is a remote, streamable-HTTP endpoint at https://api.openstatus.dev/mcp. It exposes 9 tools scoped to a single workspace.
Connect
Add this to your MCP client config (Claude Desktop, Cursor, ChatGPT custom connector, etc.):
{
"mcpServers": {
"openstatus": {
"type": "http",
"url": "https://api.openstatus.dev/mcp",
"headers": {
"x-openstatus-key": "os_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}
The x-openstatus-key header is the same API key used by the CLI, REST API, and Terraform provider. Generate one in Settings → API Tokens. There is no separate MCP OAuth flow.
Tools
list_status_pages— discover pages the workspace owns.list_page_components— discover the components on a page (id, name, type, linked monitor). Resolves thepageComponentIdsaccepted by the create/update tools below.list_status_reports— read incidents on a page.list_maintenances— read scheduled maintenance windows.create_status_report— open a new incident.add_status_report_update— post an update on an open incident.resolve_status_report— close an incident.update_status_report— edit incident metadata.create_maintenance— schedule a maintenance window.
Every mutation tool requires an explicit notify: true | false argument. The model must decide whether subscribers are paged. There is no implicit default.
Audit
All MCP mutations are written to the workspace audit log with actor_type = 'mcp', so any change can be traced back to a key, a user, and the MCP transport.
Reference
- Full tool schemas and error codes: https://www.openstatus.dev/docs/reference/mcp-server/
- Product overview: https://www.openstatus.dev/tooling/mcp-server