MCP Server
Connect Claude, ChatGPT, Cursor, and any other Model Context Protocol client to your workspace — chat-shaped AI access with audit-logged mutations and explicit notify semantics.
The openstatus MCP server connects Claude Desktop, ChatGPT, Cursor, and any other Model Context Protocol client to your workspace — so an AI assistant can read and update status pages, status reports, and maintenance windows directly from a conversation.
Quickstart
{
"mcpServers": {
"openstatus": {
"url": "https://api.openstatus.dev/mcp",
"headers": {
"x-openstatus-key": "os_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}
Drop the snippet into your client's MCP config (claude_desktop_config.json, Cursor settings, ChatGPT custom connector), restart, and the openstatus tools appear in the picker. The server is stateless Streamable HTTP and scales horizontally.
What you can do
The server exposes 8 tools scoped to your workspace:
list_status_pages— discover the pages your assistant can act on.list_status_reports/create_status_report— read and post incidents.append_status_report_update/resolve_status_report— drive an incident through its lifecycle.update_status_report— edit metadata after the fact.create_maintenance/update_maintenance— schedule and adjust planned downtime.
Every mutation tool requires notify: true | false — the assistant must explicitly choose whether to notify subscribers, so an LLM cannot quietly fan out an alert.
Auth & audit
Authentication is the x-openstatus-key header — the same API key the CLI, API, and Terraform use. We don't implement the MCP OAuth flow: no separate credential to manage, no consent screen, just one key from Settings → API Tokens.
Every mutation lands in the audit log under actor_type = 'mcp', so you can trace any change back to a key, a user, and a transport.
Other surfaces
- Want a terminal interface for AI agents (Claude Code, etc.) instead of chat? See skills on the CLI page.
- Building an in-app integration? Call the API directly.
- Want Slack instead of Claude or ChatGPT? See the Slack agent.
Reference
Full tool schema, error codes, and per-client config in the MCP reference.