UptimeRobot

UptimeRobot for AI agents

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 folders — installable plugin manifests for Claude Code, Cursor, and Codex.
• skills folder — workflow skills (setup, no-account quick monitor, bulk pause, SLA reports, incident response, status pages) plus short per-tool reference pages that cover only what the MCP tool schemas don't say. See Skills.
• rules folder — Cursor rules (.mdc). Claude Code gets the same rules from the conventions skill.
• 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.
• The assets folder — the 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 connect directly to the hosted server at https://mcp.uptimerobot.com/mcp over streamable HTTP. Nothing runs locally: the client discovers the server's OAuth endpoints and runs the browser login itself. 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.).

Install

Claude Code

From the marketplace (once published)

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.

Local clone (manual plugin install)

To run the full plugin (skills 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.gitclaude --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.

MCP server only (scripted)

If you just want the MCP tools without the rest of the plugin (dotfiles, CI bootstrap), see skills/setup/SKILL.md. Short version:

claude mcp add --transport http uptimerobot https://mcp.uptimerobot.com/mcp

Then run /mcp, select uptimerobot, and choose Authenticate to complete the OAuth browser flow. Run /mcp (or claude mcp list in a terminal) to confirm uptimerobot shows ✓ connected.

Cursor

From the Marketplace (once published)

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.

Local install (for development and pre-submission testing)

Follow Cursor's plugin docs:

# Clone or symlink this repo into Cursor's local plugin foldergit 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:

• Settings → Rules, Skills, Subagents — the uptimerobot.mdc rule and every skills/*/SKILL.md entry should be listed.
• Settings → Tools & MCPs — uptimerobot should appear with up to 50 tools (fewer for read-only or team sessions) once the MCP server connects. Complete the OAuth browser flow on first connection.

Codex

Local install (for development and pre-submission testing)

Clone the repo and open it in Codex. The repo-scoped marketplace at .agents/plugins/marketplace.json is auto-discovered, so UptimeRobot (local) will appear in the Codex plugin directory without any extra setup. Install the plugin, then complete the OAuth browser flow on first MCP connection.

If you want Codex to track the source explicitly:

codex plugin marketplace add ./

Verify the plugin is loaded: the UptimeRobot skills should be available and the uptimerobot MCP server should appear with up to 50 tools (fewer for read-only or team sessions) once connected.

Other agents / direct MCP

The server is listed in the official MCP Registry as com.uptimerobot/uptimerobot, so any registry-aware client can discover and install it without a per-client plugin submission. Metadata lives in server.json:

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

Clients without registry support can connect to the same URL directly (OAuth on first use):

{  "mcpServers": {    "uptimerobot": {      "type": "http",      "url": "https://mcp.uptimerobot.com/mcp"    }  }}

Headless / CI (no browser)

Where the OAuth browser flow can't run, add the server to your own client config with an API key from the dashboard (Integrations & API) instead — a Read-only key unless the job needs to write. Keep the key in an environment variable, not in the file, and never commit it. This is a manual setup — the plugin itself never reads or sends an API key:

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

Claude Code expands ${UPTIMEROBOT_API_KEY} from the environment; other clients have their own syntax (Cursor: ${env:UPTIMEROBOT_API_KEY}).

What the plugin provides

50 tools via MCP, grouped by resource — full list in AGENTS.md; each tool's own schema and description are the reference for its parameters:

Monitors

Monitor groups (create/update/delete plan-gated: monitor-groups)

Status pages (PSPs)

PSP announcements (plan-gated: psp-subscribers)

Maintenance windows (plan-gated: maintenance-window)

Incidents

Incident comments (plan-gated: incident-comments)

Alert contacts (personal)

Integrations & tags

Account & storm protection

Alert contact IDs for assignedAlertContacts come from list-alert-contacts (personal) and list-integrations (which also returns the account's personal contacts — dedupe by id, and tell them apart by type); each entry needs alertContactId, threshold, and recurrence. All delete-* tools are permanent — call get-user first to confirm which account the session acts on.

No account needed

The quick-monitor-setup skill 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/.

Skills

The tools' own schemas cover parameters, so the skills focus on multi-step workflows and on behaviour the schemas don't spell out.

Workflows

Reference pages — short notes on non-obvious behaviour, verified against the live server: create-http-monitor, create-keyword-monitor, create-ping-monitor, create-port-monitor, create-heartbeat-monitor, create-dns-monitor, create-api-monitor, create-udp-monitor, update-monitor, manage-monitors, manage-monitor-groups, maintenance-windows, list-integrations, stats, incidents, errors.

Plan requirements

Plan names change over time — read the active plan from get-user (activeSubscription.plan, e.g. Scale) instead of assuming a fixed list. Monitor-type availability, interval minimums, and monitor limits depend on the active plan — the MCP server enforces these and returns a plain-text error. Tool calls are rate-limited too (10 per minute on the free plan). See skills/errors/SKILL.md.

Troubleshooting

Tools not showing up in Claude / Cursor

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 in Claude Code: fully quit (close the terminal, not just /exit) and relaunch; run claude mcp list first to confirm uptimerobot shows ✓ Connected. Fix in Cursor: reload the window or restart Cursor, and check Settings → Tools & MCPs.

Authentication problems

Tool errors

Tool errors arrive as plain text whose wording varies by tool. What each message means and how to recover is in skills/errors/SKILL.md.

Contributing

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

Privacy & Terms

• Privacy Policy
• Terms of Service

License

MIT. See LICENSE.