
openstatus
dev.openstatusPublished by openstatus.devOfficial publisherv1.0.0Updated Nov 2, 2026
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Overview
Remote MCP server for openstatus that lets an assistant manage uptime monitors, status pages, incidents and maintenance windows in a workspace.
- What you can do
- Manage monitors and status pages in the openstatus workspace
- Declare, update and resolve incidents, including severity, commander and timeline
- Handle maintenance windows and status page content
- Work alongside the openstatus dashboard, CLI, Terraform and API, which share one API key
- When to use it
- Useful when a team runs uptime monitoring and status pages on openstatus and wants an AI assistant to declare or update incidents, adjust monitors, or maintain status pages without switching to the dashboard.
- Requirements
- A remote MCP endpoint at api.openstatus.dev with OAuth authentication required; an openstatus workspace account. No environment variables or headers are declared.
Installation
In SourceWeft
- Open openstatus in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.openstatus%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"openstatus": {
"type": "http",
"url": "https://api.openstatus.dev/mcp"
}
}
}README
openstatus
The open-source status page, incident response and uptime monitoring platform.
Learn more »
Documentation
·
Website
·
Discord
[License] [GitHub stars] [Discord]
About openstatus
openstatus is the open-source status page, incident response and uptime monitoring platform built for infra as code. Run incidents from Slack or your AI agent. Declare monitors and status pages in code. Let your agents update them.
Monitors, status pages, and notification channels are declared in YAML or Terraform, applied from the CLI or CI, and operable from Claude, ChatGPT, or Cursor over MCP. Available as a managed service or self-hosted.
Why openstatus?
- Infra as code — monitors, status pages, and notifications in YAML or Terraform, applied from the CLI or CI
- Built for humans and agents — MCP server,
--jsonCLI, typed API, read-only or read-write key scopes, every mutation in the audit log - Status pages + monitoring in one tool — no need to wire up a separate monitoring service
- 28 global regions checking in parallel across 3 cloud providers
- Flat pricing, unlimited members — no per-seat or per-subscriber charges
- Open source & self-hostable — AGPL-3.0, private-locations run in a single 8.5MB Docker image
- Incident response — declare and run incidents from the dashboard or Slack, with severity, commander, and a full timeline
- Incident communication — subscriber notifications via email, RSS, and webhooks
Status pages
Beautiful, customizable status pages with custom domains, password protection, maintenance windows, and subscriber notifications via email and RSS. Build trust and keep your users informed during incidents.
Uptime Monitoring
Monitor your servers, websites and APIs from 28 regions across multiple cloud providers globally. Get notified via Slack, Discord, PagerDuty, email, and more when your services are down or slow.
Incident response
Declare, coordinate, and resolve incidents from the dashboard or right inside Slack.
- Dashboard — declare an incident, set its severity (critical, major, minor), assign a commander, and move it from open → mitigated → resolved. Every change lands on the incident timeline.
- Slack — mention the openstatus agent to declare, update, resolve, or add notes to an incident without leaving the conversation. Bind an incident to a Slack channel so the team coordinates in one place.
- Status page updates — link a status report to an incident so your users see what your team is working on.
- Agents — the same incident tools are available over MCP, so Claude, ChatGPT, or Cursor can manage incidents too.
Recognitions
[openstatus | Trendshift] [Featured on Hacker News] [openstatus - #2 Product of the Day on Product Hunt]
Tooling
Everything the dashboard does is reachable from your terminal, your infrastructure code, and your AI assistant — all sharing a single API key.
- API — typed JSON-over-HTTP (ConnectRPC) with a Node SDK
- CLI — interactive for humans,
--jsonfor agents, YAML monitoring as code - Terraform — monitors, notifications, and status pages as HCL
- MCP server — connect Claude, ChatGPT, Cursor, or any MCP client to your workspace
Getting Started
With Docker (Recommended)
The fastest way to get started for both development and self-hosting:
Full guide: DOCKER.md
Self-Hosting with Coolify
We provide pre-built Docker images for easy deployment:
Complete Coolify Deployment Guide
Self-Hosting with Railway
Deploy the full stack (dashboard, status pages, API, workflows, probes, libSQL, and Tinybird Local) to one Railway project with one click:
The template source and the setup instructions are in ephraimduncan/openstatus-railway.
Manual Setup
Requirements
Dashboard
See apps/dashboard/README.md for full steps (env, db, login, troubleshooting).
Status page
- Install dependencies
pnpm install
- Run the server
pnpm -w dev:status-page.
Web (marketing site)
- Install dependencies
pnpm install
- Run the server
pnpm -w dev:web.
Tech Stack
- Next.js - Dashboard
- Hono - API server
- Go - Checker
- Turso - Database
- Drizzle - ORM
- Tinybird - Analytics
- Tailwind CSS - Styling
- shadcn/ui - UI components
Contributing
If you want to help us build the best status page and monitoring platform, check our contributing guidelines.
[Image][openstatus repository activity]
Contact
Interested in our enterprise plan or need special features? Email us at [email protected] or book a call.
License
Distributed under the AGPL-3.0 License.
Source: README.md at commit 734d10a
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts