# openstatus — MCP server card for AI agents

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

Registry name: `dev.openstatus/mcp` · category: Other · version 1.0.0 · updated 2026-09-10

## Connect
- Remote (Claude Code): `claude mcp add --transport http openstatus https://api.openstatus.dev/mcp`

## Facts
- Repository: https://github.com/openstatusHQ/openstatus (9,274 stars)
- Website: https://www.openstatus.dev

Before you connect a server: read its repository, and give it only the permissions and keys it needs.

## Links
- AgentGid page: https://agentgid.com/mcp/servers/dev-openstatus-mcp/


## openstatus: run status pages and uptime checks from chat

openstatus checks that your website or service is up and shows a public status page to your users. Its MCP server lets your AI assistant read those checks, post incident updates, schedule maintenance and set up new pages from a chat. You sign in once in the browser and pick what it may change.

### Where to use it
- Tell users about an outage fast: When something breaks, ask the assistant to draft a public status update. It shows you the draft and asks whether to email subscribers before posting.
- Find out what is failing: Ask "what is failing right now?" and the assistant reads each region's health and the latest check results, with status codes and timings.
- Announce planned maintenance: Plan a database upgrade for Sunday night and let the assistant put the window on your status page, with or without telling subscribers.
- Set up checks and a page for a new app: Launching a new site? The assistant adds an uptime check for its address, creates a status page and puts the check on it.
- Run an incident and write the postmortem: Open an internal incident, add notes as you work, then let the assistant draft the postmortem from the timeline for you to approve.
- A weekly uptime summary: Every Monday, ask the assistant for each check's success rate and response times over the last 7 days and paste it into your team update. (idea, not from the official pages)

### How to start
- Add the server to your AI app (Claude Code shown; the docs also cover Codex, Cursor, ChatGPT and others).

```
claude mcp add --transport http --scope user openstatus https://api.openstatus.dev/mcp
```

- Approve in the browser, picking the workspace and the access level (Read only, Read and write, or Custom).
- For a server or CI job with no browser, send an API key in the x-openstatus-key header instead.

### License
openstatus is open source under the AGPL-3.0, and the hosted service starts with a free Hobby plan. If you change its code and run it for others, you must share your changes under the same license.

### Good to know
- Some tools post on your public status page and can email subscribers. The assistant must decide each time whether to notify, and a skipped notice cannot be sent later.
- You choose what it may change. A Read only connection sees only the list and get tools.
- It cannot delete checks, pages or groups, or edit alert channels, custom domains and page themes; those stay in the dashboard. It can delete single updates.
- Every change made this way is written to the workspace's change log, and new checks, pages and parts are capped at 30 per hour.
- The free plan has 1 check and 1 status page; more needs a paid plan.

Checked 2026-11-10 against: https://www.openstatus.dev, https://www.openstatus.dev/llms.txt, https://www.openstatus.dev/docs/reference/mcp-server, https://www.openstatus.dev/docs/reference/mcp-server.md, https://www.openstatus.dev/docs/guides/how-to-connect-openstatus-to-your-agent.md, https://www.openstatus.dev/tooling/mcp-server.md, https://github.com/openstatusHQ/openstatus/blob/bba13ddc9e304695547f039cff849ed7e9826c58/README.md, https://github.com/openstatusHQ/openstatus/blob/bba13ddc9e304695547f039cff849ed7e9826c58/LICENSE, https://github.com/openstatusHQ/openstatus/blob/bba13ddc9e304695547f039cff849ed7e9826c58/apps/server/server.json, https://github.com/openstatusHQ/openstatus/blob/bba13ddc9e304695547f039cff849ed7e9826c58/apps/server/MCP_REGISTRY.md, https://github.com/openstatusHQ/openstatus/blob/bba13ddc9e304695547f039cff849ed7e9826c58/apps/server/src/routes/mcp/server.ts, https://github.com/openstatusHQ/openstatus/blob/bba13ddc9e304695547f039cff849ed7e9826c58/apps/server/src/routes/mcp/tools/registry-adapter.ts, https://github.com/openstatusHQ/openstatus/tree/bba13ddc9e304695547f039cff849ed7e9826c58/packages/services/src/agent-tools, https://registry.modelcontextprotocol.io/v0/servers/dev.openstatus%2Fmcp/versions/latest

### Mistakes to avoid
- Don't: Calling create_status_report without notify, or deciding notify yourself → Do: Show the draft, ask the person whether to notify subscribers, then pass notify true or false (The field is required with no default, and a notice sent without notify can never be sent to subscribers later.)
- Don't: Typing a page, monitor or component id from memory → Do: Look it up with list_status_pages, list_page_components or list_monitors first (Ids from outside the workspace or the page come back as NOT_FOUND.)
- Don't: Sending update_monitor with only the new alert channel in notificationIds → Do: Read the monitor with get_monitor and send the existing ids plus the new one (Array fields replace the stored set, so a partial list unlinks the other channels.)
- Don't: Assuming resolve_incident also closes the public status report → Do: Call resolve_status_report as well when the public notice is still open (Internal incidents and public reports are resolved separately.)
- Don't: Reading notified true as proof that every subscriber got the message → Do: Treat it as "the sending step ran"; check delivery in the dashboard if it matters (The flag only says the dispatch call did not fail.)

### Questions
- Do I have to paste an API key? No. Interactive AI apps sign in through a browser consent screen; an API key is only the fallback for CI and servers.
- How many tools does it have? 50, or 48 on plans without the audit log; 4 of them read public openstatus.dev pages.
- How do I cut off the assistant's access? Revoke the connection under Settings, Integrations, Connected apps; its next call fails.
- Does declaring an incident publish anything? No. Incident tools are internal; only status reports and maintenance tools publish to the status page.

---
AgentGid's catalog is curated: every entry was checked against the maker's official pages (registry, repository, license and pricing pages) on the date shown; a license value shows the quote it stands on wherever AgentGid has one. Usage numbers come from AgentGid's own scan of public repositories set up for AI coding agents. Claims by makers are reported, not tested by AgentGid.
