Openstatus

What the openstatus MCP server does

The openstatus MCP server gives an AI client access to operational resources in an openstatus workspace. Its supported scope includes uptime monitors, public status pages, incidents, and maintenance windows. This makes it suitable for agents that need to review service status, change monitoring configuration, publish status information, or coordinate incident work.

openstatus combines uptime monitoring and status-page management in one platform. Monitors can check servers, websites, and APIs from 28 global regions across three cloud providers. Status pages can use custom domains, password protection, maintenance windows, and subscriber notifications through email and RSS. Incident workflows include severity, an assigned commander, state changes, notes, and a timeline.

How it works

The MCP connection operates against an openstatus workspace rather than directly against a local configuration file. Key scopes can be read-only or read-write, and mutations are recorded in an audit log.

An agent can use the MCP interface alongside existing infrastructure-as-code workflows. Monitors, status pages, and notification channels can also be declared in YAML or Terraform and applied through the CLI or continuous-integration systems. This allows teams to reserve declarative configuration for repeatable changes while using the openstatus MCP server for conversational inspection or operational updates.

Setup and configuration

The repository presents openstatus as available either as a managed service or as a self-hosted platform. Its documented self-hosting paths include Docker, Coolify, and Railway. The Docker quick start copies an environment file, starts the service with Docker Compose, and exposes the dashboard on port 3002 and status pages on port 3003.

It does establish that the tooling uses a single API key, so access requires credentials for the target workspace. Exact setup instructions should be taken from the project’s MCP documentation before deploying a client connection.

Tools and capabilities

The openstatus MCP server is intended for these operational tasks:

• Managing uptime monitors for services, websites, and APIs.
• Creating or updating status pages and their operational settings.
• Declaring, updating, and resolving incidents.
• Adding incident notes and maintaining an incident timeline.
• Managing maintenance windows.
• Connecting incident activity with status-page communication.

Incident management is also available from the dashboard and Slack. The README specifically states that the same incident tools are available over MCP, including incident declaration, updates, resolution, and notes. Subscriber communication can use email, RSS, and webhooks, while service alerts can be sent through channels including Slack, Discord, PagerDuty, and email.

Limitations and notes

It also does not document whether every dashboard or CLI operation is exposed through MCP; the clearest MCP-specific scope is workspace access for monitors, status pages, incidents, maintenances, and the incident operations described above.

Read-only and read-write key scopes are available, so deployments should choose credentials according to whether the agent only observes workspace state or is allowed to make changes. Because mutations are placed in the audit log, teams can review agent-driven updates through the same operational history as other changes.