By uptimerobot
Monitor websites, APIs, and servers — create HTTP, keyword, ping, port, heartbeat, DNS, API, and UDP monitors, triage incidents with diagnostics and traceroute, generate SLA reports and health snapshots, schedule maintenance windows, and publish status pages, all from Claude Code using the UptimeRobot API.
Pause (or resume) many UptimeRobot monitors at once — by tag, search term, or state — around a deployment or maintenance window.
Conventions and gotchas for every UptimeRobot MCP tool call — monitor types, URL formats, HEARTBEAT URL handling, discovery-before-writes, pagination, time ranges, error codes, and output style. Use whenever you call any uptimerobot:* tool.
Create an API monitor that calls an HTTP endpoint and runs up to five JSON/header assertions combined with AND/OR logic; alerts when assertions fail.
Create a DNS monitor that resolves records for a domain and alerts when they change or the DNS server does not respond.
Create a HEARTBEAT monitor (cron/job monitor) that expects the target to ping a generated URL on a schedule; alerts when expected pings stop arriving.
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This repo is UptimeRobot's single source of truth for AI agent integrations. It publishes:
**llms.txt** and **AGENTS.md** — discovery and orientation for LLMs and coding agents.**.claude-plugin/****, **.cursor-plugin/**, and ****.codex-plugin/** — installable plugin manifests for Claude Code, Cursor, and Codex.**skills/** — self-contained skill files covering every UptimeRobot MCP tool plus onboarding and runbook workflows.**rules/** — shared rules loaded by both Cursor and Claude Code.**mcp.json** — Cursor-format MCP server config (dot-less filename).**.mcp.json** — Claude Code MCP server config (dot-prefixed so Claude Code auto-registers the server when the plugin loads).**codex.mcp.json** — Codex-format MCP server config (mcp_servers snake_case key, referenced explicitly by the Codex manifest).**.agents/plugins/marketplace.json** — repo-scoped Codex marketplace for local install and testing; Codex auto-discovers this file when the repo is open.**assets/logo.png** — marketplace logo, declared as the icon in the Cursor and Codex manifests (Claude Code's plugin manifest has no icon field; the directory listing supplies its icon at submission time).The mcp.json, .mcp.json, and codex.mcp.json files all register the same mcp-remote launcher that proxies to https://mcp.uptimerobot.com/mcp and runs the OAuth browser flow. Three filenames exist only because Claude Code, Cursor, and Codex each expect their own convention (and Codex requires mcp_servers in snake_case rather than mcpServers).
The same content is mirrored under uptimerobot.com/ for crawler discovery (uptimerobot.com/llms.txt, uptimerobot.com/AGENTS.md, etc.).
UptimeRobot is being submitted to Anthropic's community plugin marketplace. Once accepted, add that marketplace once and install:
/plugin marketplace add anthropics/claude-plugins-community
/plugin install uptimerobot@claude-community
Or run /plugin, open the Discover tab, find UptimeRobot, and install it. (The community marketplace must be added first — it isn't built in. Only Anthropic's curated official marketplace shows up in /plugin with no setup.)
The MCP server auto-registers via .mcp.json as soon as the plugin loads. The first time it connects, a browser opens for you to log into UptimeRobot and authorize access (OAuth) — there's no API key to paste. Tokens are cached locally, so you only do this once.
To run the full plugin (skills, rules, commands, and the auto-registered MCP server) straight from a local checkout — no marketplace required — clone the repo and load it with the --plugin-dir flag:
git clone https://github.com/uptimerobot/ai.git
claude --plugin-dir ./ai
--plugin-dir <path> loads the plugin from a directory (the one containing .claude-plugin/plugin.json) for that session only. The flag is repeatable and also accepts a .zip. Use an absolute path if you launch Claude Code from elsewhere:
claude --plugin-dir /absolute/path/to/ai
On first connection a browser opens for the OAuth flow. Run /plugin to confirm the plugin is loaded and uptimerobot MCP Server shows ✓ connected.
If you just want the MCP tools without the rest of the plugin (dotfiles, CI bootstrap), see [skills/setup/SKILL.md](skills/setup/SKILL.md). Short version:
claude mcp add uptimerobot -- npx -y mcp-remote@latest https://mcp.uptimerobot.com/mcp
Then quit and relaunch Claude Code, completing the OAuth browser flow when it appears. Run /plugin to confirm uptimerobot MCP Server shows ✓ connected.
Browse the Cursor Marketplace, find UptimeRobot, and click Add to Cursor. Authorize through the OAuth browser flow when the MCP server first connects — no API key needed.
Follow Cursor's plugin docs:
# Clone or symlink this repo into Cursor's local plugin folder
git clone https://github.com/uptimerobot/ai.git ~/.cursor/plugins/local/uptimerobot-ai
Launch Cursor and run Developer: Reload Window from the command palette.
Verify the plugin is discovered:
uptimerobot.mdc rule and every skills/*/SKILL.md entry should be listed.uptimerobot should appear with 32 tools once the MCP server connects. Complete the OAuth browser flow on first connection.npx claudepluginhub uptimerobot/aiClaude plugins for Better Stack - uptime monitoring, incident management, status pages, on-call schedules, and log management (Logtail) for MSPs
Set up synthetic monitoring for proactive performance tracking
DevsForge site reliability engineering specialist for building resilient and scalable systems
Monitoring and alerting configuration with dashboard generation
🐉 Specialised SRE skills for outage investigations, monitoring graphs, and post-mortems on Google Cloud Platform.
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications running smoothly while preparing for growth and preventing disasters. Examples:\n\n<example>\nContext: App experiencing slow performance