Skip to main content

comparing monitoring as code

Which uptime monitors ship an MCP server?

An MCP server lets an assistant read your monitoring and, sometimes, change it. A year ago almost nobody in this category had one. That is no longer the story, so here is the actual state of it, checked against vendor docs rather than announcements.

who actually ships one

  UptimepageBetter StackUptimeRobotChecklyOpenStatusPingdom
official MCP server yesyesyesyesyesnone
hosted endpoint yesyesyesyesyesnone
OAuth sign-in yesyesyesyesAPI key onlynone
writes fenced, you approveyesyesyesscoped by keynone
covers status pages yesyesyesyesyesnone

Hosted, OAuth-authenticated MCP servers are common in this category as of July 2026, not a differentiator. Better Stack, UptimeRobot and Checkly all ship one, as do Datadog, Grafana Cloud, Sentry and PagerDuty in the wider observability space.

StatusCake and Pingdom ship no MCP server. Atlassian's official server covers Jira, Confluence, Bitbucket and Compass, and explicitly does not cover Statuspage.

OneUptime ships a hosted server with roughly 155 tools, authenticated with a project-scoped API key rather than OAuth.

Uptime Kuma has no official MCP server. A dozen or so community wrappers exist, all local and pointed at an instance you run.

Verified against each vendor's documentation on 14 July 2026.

This is table stakes now, not a differentiator

We would rather say this plainly than have you find out. Hosted, OAuth-authenticated MCP servers with write actions are shipping across the category: Better Stack, UptimeRobot and Checkly all have one, and Checkly's arrived in June 2026. Datadog, Grafana Cloud, Sentry and PagerDuty have them in the wider observability space. OpenStatus and OneUptime ship servers too, though both stop at API-key auth rather than OAuth. If a vendor tells you their MCP server makes them unique, check the others.

The interesting fact is who is missing

As of July 2026, StatusCake ships no MCP server. Pingdom ships no MCP server, and nothing customer-connectable appears anywhere in SolarWinds' product documentation. Atlassian has an official MCP server, and it covers Jira, Confluence, Bitbucket and Compass while explicitly not covering Statuspage. Uptime Kuma has no official server either; what exists is a dozen community wrappers, all local, pointed at your own instance. If an assistant reading your monitoring matters to you, that shortlist matters more than any feature table.

Hosted or local, and why it matters

A hosted server is a URL you point a client at, with the vendor handling auth and updates. A local one is a process you run, holding a key, usually over stdio. Local is fine for a workstation and awkward for a team, because every person who wants it has to install and credential it themselves. The self-hosted tools land on the local side by nature, which is not a criticism so much as a consequence of where they run.

Ask what it can change, not just what it can read

Reading is the easy half. The question worth asking a vendor is what an assistant is allowed to do, and what stands between a confused model and your production monitoring. The emerging norm is a fence of some kind: PagerDuty ships read-only until you pass a flag, Grafana Cloud makes you consent to writes at authorization time, OpenStatus filters mutating tools out for read-only keys and forces an explicit notify flag, OneUptime annotates its destructive tools. Uptimepage takes the same line: reads are open, and every write asks you first and is audited afterwards.

Where Uptimepage fits

Uptimepage's MCP server runs in-process at mcp.uptimepage.dev, with one-click OAuth, the same tenant isolation, scopes and rate limits as the dashboard, and writes fenced behind your approval. It covers monitors, incidents and status pages, so an assistant can tell you what is broken, how long it has been broken and what you told customers about it. That combination is good, and it is not rare, and both of those things are true. Hosted free with no card, or self-host it under AGPL.

links

FAQ

Which uptime monitoring vendors ship an MCP server?
As of July 2026: Better Stack, UptimeRobot, Checkly, OpenStatus, OneUptime and Uptimepage. Better Stack, UptimeRobot and Checkly authenticate with OAuth like Uptimepage does; OpenStatus and OneUptime use API keys.
Does Pingdom or StatusCake have an MCP server?
Neither does. Nothing customer-connectable appears in StatusCake's docs or in SolarWinds' product documentation for Pingdom. Atlassian's official MCP server covers Jira, Confluence, Bitbucket and Compass, and explicitly does not cover Statuspage.
Does Uptime Kuma have an MCP server?
No official one. A dozen or so community wrappers exist, all local and pointed at your own instance, with the most active being a TypeScript server that speaks to Kuma over its socket API. There is no hosted endpoint, which follows from Kuma being self-hosted by nature.
Can an assistant change my monitoring over MCP?
It depends on the vendor, and it is the question worth asking. Uptimepage fences every write behind your explicit approval and audits it. Others take similar lines: PagerDuty ships read-only until you enable writes, Grafana Cloud asks for write consent during authorization, and OpenStatus hides mutating tools from read-only keys.

Start in under 5 minutes.

Start free

features · pricing · notes