The coverage runs well past creating monitors: maintenance windows suppress alerts around planned work, status pages and announcements are how you tell users what is happening, and incident comments keep the write-up where the incident is. The quick-monitor-setup path is the unusual one — a free HTTPS monitor from an email address alone, confirmed by clicking a link — which makes "start watching this URL" something an agent can do for a person who has never signed up.
UptimeRobot's own hosted server at mcp.uptimerobot.com, reached through mcp-remote with an OAuth browser flow. It covers monitors and monitor groups, public status pages and their announcements, maintenance windows, incidents and their comments, plus alert integrations and tags.
- Monitors created in any of its types — HTTP, KEYWORD, PING, PORT, HEARTBEAT, DNS, API, UDP — then renamed, re-pointed, re-intervalled, paused or resumed
- Monitors listed with search and state filters, one monitor's full config and current state, and aggregated up, down and paused counts with uptime percentage
- Bucketed response-time series, for looking at a slowdown rather than only an outage
- Public status pages built from monitors, groups or tags, with domain, sort order, visibility and publish status
- Status-page announcements posted as info, maintenance or issue, then edited, pinned and unpinned
- Maintenance windows scheduled one-off or recurring, so alerts stay quiet through planned work
- Incidents listed across monitors by time range, and one incident opened up to its checker locations, logs and traceroute
- Comments added to an incident and edited, keeping the write-up attached to the incident itself
- The alert-contact integrations available on the account, and the account's tags
- A free HTTPS monitor created from someone's email address alone — no account, no key — confirmed by clicking a link in the activation mail
An UptimeRobot account. The default route is npx -y mcp-remote@latest https://mcp.uptimerobot.com/mcp, which opens a browser once for OAuth and caches the token — no API key to paste. Where no browser can run, connect over plain HTTP to the same URL with a Main API key from the dashboard's Integrations & API page, sent as an Authorization: Bearer header. Monitor types, minimum intervals and monitor counts follow your plan and the server enforces them, returning -28002 when a call would go past what the plan allows; monitor groups, maintenance windows and incident comments are themselves plan-gated. The repository also ships Claude Code, Cursor and Codex plugin manifests that register the server for you.
One command — claude mcp add uptimerobot -- npx -y mcp-remote@latest https://mcp.uptimerobot.com/mcp