openstatus MCP server
The openstatus MCP server is a remote, streamable-HTTP endpoint at https://api.openstatus.dev/mcp. It exposes 23 tools (21 on plans without the audit-log feature): 19 scoped to a single workspace plus 4 that search and read public openstatus.dev content.
Connect
OAuth (recommended for interactive clients)
Point the client at the endpoint with no header. The server answers 401 with a WWW-Authenticate header, and any client implementing the MCP authorization spec (Claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, Codex, opencode, VS Code) registers itself, opens the consent screen, and exchanges the code for an os_oat_… bearer token via PKCE. On the consent screen you pick the workspace and the access level (read-only or read & write). Nothing to copy.
{
"mcpServers": {
"openstatus": {
"type": "http",
"url": "https://api.openstatus.dev/mcp"
}
}
}
claude mcp add --transport http --scope user openstatus https://api.openstatus.dev/mcp
Connected apps are listed under Settings > Integrations > Connected apps, where they can be revoked at any time.
API key (CI, cron, headless agents)
Send an openstatus API key in the x-openstatus-key header. It is the same key used by the CLI, REST API, and Terraform provider; create one in Settings > General, in the API Keys card. When both credentials are present, the header wins.
{
"mcpServers": {
"openstatus": {
"type": "http",
"url": "https://api.openstatus.dev/mcp",
"headers": {
"x-openstatus-key": "os_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}
Scopes
Both credentials carry a scope. Read-only credentials only see list_* and get_* tools in tools/list; mutation tools are not registered and cannot be called. Read & write exposes every tool. An API key's scope is fixed at creation; an OAuth grant's scope is chosen on the consent screen.
Tools
Status pages
list_status_pages — discover pages the workspace owns. Resolves the pageId required by the mutation tools.
list_page_components — discover the components on a page (id, name, type, linked monitor). Resolves the pageComponentIds accepted by the create/update tools below.
Status reports
list_status_reports — read incidents on a page (filter: "active" | "all", paginated).
create_status_report — open a new incident.
add_status_report_update — post an update on an open incident.
update_status_report — edit incident metadata (title, status, components) without a public update.
resolve_status_report — close an incident with a final update.
Maintenance
list_maintenances — read scheduled maintenance windows (paginated).
create_maintenance — schedule a maintenance window (from / to as ISO 8601).
Monitors (read-only)
list_monitors — list monitors with activeIncidentCount. Resolves the numeric monitorId the other monitor tools require.
get_monitor — full configuration: URL, regions, periodicity, retries, notification channels, tags.
get_monitor_status — per-region current health (active / degraded / error).
get_monitor_summary — success/degraded/error counts and p50–p99 latency over 1d, 7d, or 14d.
list_response_logs — recent per-region check results (status code, latency, attempts) over 1d, 7d, or 14d. HTTP monitors only.
get_response_log — one check in full: attempts, timing breakdown, redacted headers, error, assertion results.
Workspace (read-only)
list_notifications — notification channels and the monitors wired to each. Credentials are never exposed.
list_private_locations — private locations with status and lastSeenAt. Agent tokens are never exposed.
list_audit_logs — audit-log entries, last 14 days, optional entityType + entityId filter. Requires the audit-log plan feature.
get_audit_log — before/after snapshots and changedFields for one entry. Requires the audit-log plan feature.
Content (read-only, public)
Public openstatus.dev pages — no workspace data, available on any credential and any scope.
search_docs — search documentation, guides, or changelog (type, default docs). Returns a path for get_doc_page.
get_doc_page — full markdown of one docs, guide, or changelog page by path.
search_content — search every public page: product/pricing, blog, comparisons, use cases, customer stories, tooling, plus docs/guides/changelog (type, default all). Returns a path for get_content_page.
get_content_page — full markdown of any public page by path (e.g. pricing, blog/…, compare/…). Use it for "which plan fits" or "how does openstatus compare to X" questions.
Resources
The server also exposes three read-only resources on any credential: openapi-specification, mcp-server-reference, and site-index (llms.txt).
Rules for mutations
- Every publishing tool (
create_status_report, add_status_report_update, resolve_status_report, create_maintenance) requires an explicit notify: true | false argument. There is no default; the model must ask the user whether subscribers are paged. update_status_report has no notify field.
- Notifications dispatch inside the same call. An update posted with
notify: false can never be re-sent later.
- Never guess a numeric id. Call
list_status_pages and list_page_components first; ids outside the workspace come back as NOT_FOUND.
- Draft the title, status, message and components, show the draft to the user, confirm
notify, then call the tool.
Audit
All MCP mutations are written to the workspace audit log with actor_type = 'mcp', actor_id set to the credential (API key id or oat_<grant id>), and actor_user_id set to the person behind it, so any change can be traced back to a key or OAuth grant, a user, and the MCP transport.
Reference
1---2name: openstatus-mcp3description: Use the openstatus MCP server to read monitors, notification channels, private locations and audit logs, to read and update status pages, status reports, and maintenance windows, and to search the openstatus docs, pricing, and other public content from any Model Context Protocol client (Claude, ChatGPT, Cursor, Codex, opencode, etc.). Use when an AI assistant needs to check a monitor's health, post an incident, append an update, resolve a report, or schedule maintenance for an openstatus workspace.4metadata:5 source: https://skillmd.com/skills/openstatushq/openstatus-mcp6---78# openstatus MCP server910The openstatus MCP server is a remote, streamable-HTTP endpoint at `https://api.openstatus.dev/mcp`. It exposes 23 tools (21 on plans without the `audit-log` feature): 19 scoped to a single workspace plus 4 that search and read public openstatus.dev content.1112## Connect1314### OAuth (recommended for interactive clients)1516Point the client at the endpoint with no header. The server answers `401` with a `WWW-Authenticate` header, and any client implementing the MCP authorization spec (Claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, Codex, opencode, VS Code) registers itself, opens the consent screen, and exchanges the code for an `os_oat_…` bearer token via PKCE. On the consent screen you pick the **workspace** and the **access** level (read-only or read & write). Nothing to copy.1718```json19{20 "mcpServers": {21 "openstatus": {22 "type": "http",23 "url": "https://api.openstatus.dev/mcp"24 }25 }26}27```2829```bash30claude mcp add --transport http --scope user openstatus https://api.openstatus.dev/mcp31```3233Connected apps are listed under **Settings > Integrations > Connected apps**, where they can be revoked at any time.3435### API key (CI, cron, headless agents)3637Send an openstatus API key in the `x-openstatus-key` header. It is the same key used by the CLI, REST API, and Terraform provider; create one in **Settings > General**, in the **API Keys** card. When both credentials are present, the header wins.3839```json40{41 "mcpServers": {42 "openstatus": {43 "type": "http",44 "url": "https://api.openstatus.dev/mcp",45 "headers": {46 "x-openstatus-key": "os_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"47 }48 }49 }50}51```5253### Scopes5455Both credentials carry a scope. **Read-only** credentials only see `list_*` and `get_*` tools in `tools/list`; mutation tools are not registered and cannot be called. **Read & write** exposes every tool. An API key's scope is fixed at creation; an OAuth grant's scope is chosen on the consent screen.5657## Tools5859### Status pages6061- `list_status_pages` — discover pages the workspace owns. Resolves the `pageId` required by the mutation tools.62- `list_page_components` — discover the components on a page (id, name, type, linked monitor). Resolves the `pageComponentIds` accepted by the create/update tools below.6364### Status reports6566- `list_status_reports` — read incidents on a page (`filter: "active" | "all"`, paginated).67- `create_status_report` — open a new incident.68- `add_status_report_update` — post an update on an open incident.69- `update_status_report` — edit incident metadata (title, status, components) without a public update.70- `resolve_status_report` — close an incident with a final update.7172### Maintenance7374- `list_maintenances` — read scheduled maintenance windows (paginated).75- `create_maintenance` — schedule a maintenance window (`from` / `to` as ISO 8601).7677### Monitors (read-only)7879- `list_monitors` — list monitors with `activeIncidentCount`. Resolves the numeric `monitorId` the other monitor tools require.80- `get_monitor` — full configuration: URL, regions, periodicity, retries, notification channels, tags.81- `get_monitor_status` — per-region current health (active / degraded / error).82- `get_monitor_summary` — success/degraded/error counts and p50–p99 latency over `1d`, `7d`, or `14d`.83- `list_response_logs` — recent per-region check results (status code, latency, attempts) over `1d`, `7d`, or `14d`. HTTP monitors only.84- `get_response_log` — one check in full: attempts, timing breakdown, redacted headers, error, assertion results.8586### Workspace (read-only)8788- `list_notifications` — notification channels and the monitors wired to each. Credentials are never exposed.89- `list_private_locations` — private locations with status and `lastSeenAt`. Agent tokens are never exposed.90- `list_audit_logs` — audit-log entries, last 14 days, optional `entityType` + `entityId` filter. Requires the `audit-log` plan feature.91- `get_audit_log` — before/after snapshots and `changedFields` for one entry. Requires the `audit-log` plan feature.9293### Content (read-only, public)9495Public openstatus.dev pages — no workspace data, available on any credential and any scope.9697- `search_docs` — search documentation, guides, or changelog (`type`, default `docs`). Returns a `path` for `get_doc_page`.98- `get_doc_page` — full markdown of one docs, guide, or changelog page by `path`.99- `search_content` — search every public page: product/pricing, blog, comparisons, use cases, customer stories, tooling, plus docs/guides/changelog (`type`, default `all`). Returns a `path` for `get_content_page`.100- `get_content_page` — full markdown of any public page by `path` (e.g. `pricing`, `blog/…`, `compare/…`). Use it for "which plan fits" or "how does openstatus compare to X" questions.101102### Resources103104The server also exposes three read-only resources on any credential: `openapi-specification`, `mcp-server-reference`, and `site-index` (`llms.txt`).105106## Rules for mutations107108- Every publishing tool (`create_status_report`, `add_status_report_update`, `resolve_status_report`, `create_maintenance`) requires an explicit `notify: true | false` argument. There is no default; the model must ask the user whether subscribers are paged. `update_status_report` has no `notify` field.109- Notifications dispatch inside the same call. An update posted with `notify: false` can never be re-sent later.110- Never guess a numeric id. Call `list_status_pages` and `list_page_components` first; ids outside the workspace come back as `NOT_FOUND`.111- Draft the title, status, message and components, show the draft to the user, confirm `notify`, then call the tool.112113## Audit114115All MCP mutations are written to the workspace audit log with `actor_type = 'mcp'`, `actor_id` set to the credential (API key id or `oat_<grant id>`), and `actor_user_id` set to the person behind it, so any change can be traced back to a key or OAuth grant, a user, and the MCP transport.116117## Reference118119- Full tool schemas, OAuth endpoints and error codes: <https://www.openstatus.dev/docs/reference/mcp-server/>120- Product overview: <https://www.openstatus.dev/tooling/mcp-server>