UptimeRobot MCP

This repo is UptimeRobot's single source of truth for AI agent integrations. It publishes:

- llms.txtandAGENTS.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_serverssnake_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 theiconin the Cursor and Codex manifests (Claude Code's plugin manifest has no icon field; the directory listing supplies its icon at submission time).

Themcp.json,.mcp.json, andcodex.mcp.jsonfiles all register the samemcp-remotelauncher that proxies tohttps://mcp.uptimerobot.com/mcpand runs the OAuth browser flow. Three filenames exist only because Claude Code, Cursor, and Codex each expect their own convention (and Codex requiresmcp_serversin snake_case rather thanmcpServers).

The same content is mirrored underuptimerobot.com/for crawler discovery (uptimerobot.com/llms.txt,uptimerobot.com/AGENTS.md, etc.).

UptimeRobot is being submitted to Anthropic'scommunityplugin 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 theDiscovertab, findUptimeRobot, and install it. (The community marketplace must be added first — it isn't built in. Only Anthropic's curated official marketplace shows up in/pluginwith no setup.)

The MCP server auto-registers via.mcp.jsonas 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-dirflag:

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/pluginto confirm the plugin is loaded anduptimerobot MCP Servershows ✓ connected.

If you just want the MCP tools without the rest of the plugin (dotfiles, CI bootstrap), seeskills/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/pluginto confirmuptimerobot MCP Servershows ✓ connected.

Browse theCursor Marketplace, findUptimeRobot, and clickAdd to Cursor. Authorize through the OAuth browser flow when the MCP server first connects — no API key needed.

# Clone or symlink this repo into Cursor's local plugin folder git clone https://github.com/uptimerobot/ai.git ~/.cursor/plugins/local/uptimerobot-ai

The server is listed in theofficial MCP Registryascom.uptimerobot/uptimerobot, so any registry-aware client can discover and install it without a per-client plugin submission. Metadata lives inserver.json:

curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.uptimerobot/uptimerobot"

{ "mcpServers": { "uptimerobot": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.uptimerobot.com/mcp"] } } }

Where the OAuth browser flow can't run, connect over plain HTTP with a Main API key from the dashboard (Integrations & API) instead:

{ "mcpServers": { "uptimerobot": { "type": "http", "url": "https://mcp.uptimerobot.com/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }

32 tools via MCP, grouped by resource — full list and payloads inAGENTS.mdandskills/:

Monitor groups (plan-gated:monitor-groups)

Maintenance windows (plan-gated:maintenance-window)

Incident comments (plan-gated:incident-comments)

Thequick-monitor-setupskill creates a free HTTPS monitor from just someone's email, no account, API key, or OAuth: the agent calls an unauthenticated proof-of-work API and the owner confirms by clicking a link in an activation email. Guide:https://uptimerobot.com/quick-monitor-setup/.

UptimeRobot plans areFree, Solo, Team, Enterprise. Monitor-type availability, interval minimums, and monitor limits depend on the active plan — the MCP server enforces these and returns error code-28002(subscription_limit_exceeded) when a call would exceed them. Seeskills/errors/SKILL.md.

The MCP handshake sometimes completes after the client captures its tool list at session start, so the tools appear absent even though the server is connected. Fix: fully quit the client (close the terminal, not just/exit) and relaunch. Runclaude mcp listto confirmuptimerobotshows✓ Connectedbefore relaunching.

For the full error reference and recovery recipes seeskills/errors/SKILL.md.

This repo is generated / curated. File issues athttps://github.com/uptimerobot/ai/issues. For MCP server bugs, usehttps://uptimerobot.com/contact.

Interact with your AWS environment using natural language. Requires local AWS credentials.