How do I install UptimeRobot?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does UptimeRobot need an API key?

No required environment variable is listed on this record.

What transport does UptimeRobot use?

UptimeRobot is reached over HTTP.

When was UptimeRobot last checked?

Last checked 2026-10-21. Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.

UptimeRobot MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.uptimerobot.com/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

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

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.uptimerobot-uptimerobot": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.uptimerobot.com/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.1.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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/** — 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.).

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, 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.

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](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.

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 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:

Settings → Rules, Skills, Subagents — the uptimerobot.mdc rule and every skills/*/SKILL.md entry should be listed.
Settings → Tools & MCPs — uptimerobot should appear with 32 tools 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 24 skills should be available and the uptimerobot MCP server should appear with 32 tools 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 via the same mcp-remote launcher (OAuth on first use):

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

Headless / CI (no browser)

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" }
    }
  }
}

What the plugin provides

32 tools via MCP, grouped by resource — full list and payloads in [AGENTS.md](AGENTS.md) and [skills/](skills/):

Monitors

Tool	Purpose
`create-monitor`	Create HTTP, KEYWORD, PING, PORT, HEARTBEAT, DNS, API, or UDP monitors
`update-monitor`	Change name, URL, interval, alert contacts, tags, HTTP settings
`update-monitor-status`	Pause or resume a monitor
`list-monitors`	Paginated list with search + state filters
`get-monitor-details`	Full config + current state for one monitor
`get-monitor-stats`	Aggregated up/down/paused counts + uptime %
`get-response-times`	Time-series response-time data with buckets

Monitor groups (plan-gated: `monitor-groups`)

Tool	Purpose
`create-monitor-group`	Create a group and assign monitors to it
`update-monitor-group`	Rename an existing group
`get-monitor-group`	Fetch a single group by ID
`list-monitor-groups`	Paginated list of groups

Status pages (PSPs)

Tool	Purpose
`create-psp`	Create a public status page from monitors, groups, or tags
`update-psp`	Change name, domain, sort order, visibility, or publish status
`get-psp`	Fetch a single status page by ID
`list-psps`	Paginated list of status pages

PSP announcements

Tool	Purpose
`create-psp-announcement`	Post an announcement (info/maintenance/issue) to a status page
`update-psp-announcement`	Edit title, content, dates, type, or publish status
`pin-psp-announcement`	Pin an announcement to the top of the page
`unpin-psp-announcement`	Unpin an announcement
`get-psp-announcement`	Fetch a single announcement by ID
`list-psp-announcements`	Paginated list of announcements for a status page

Maintenance windows (plan-gated: `maintenance-window`)

Tool	Purpose
`create-maintenance-window`	Schedule a one-off or recurring window that suppresses alerts
`update-maintenance-window`	Change schedule, duration, monitors, or pause/resume the window
`get-maintenance-window`	Fetch a single window by ID
`list-maintenance-windows`	Paginated list of windows

Incidents

Tool	Purpose
`list-incidents`	Incidents across monitors, with time range + monitor filter
`get-incident-details`	Per-incident checker locations, logs, traceroute

Incident comments (plan-gated: `incident-comments`)

Tool	Purpose
`create-incident-comment`	Add a comment to an incident
`update-incident-comment`	Edit an existing comment
`list-incident-comments`	Paginated list of comments on an incident

Integrations & tags

Tool	Purpose
`list-integrations`	Available alert-contact integrations
`list-tags`	Paginated list of tags on the account

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/.

Plan requirements

UptimeRobot plans are Free, 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. See [skills/errors/SKILL.md](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: fully quit the client (close the terminal, not just /exit) and relaunch. Run claude mcp list to confirm uptimerobot shows ✓ Connected before relaunching.

Authentication problems

Symptom	Fix
OAuth browser didn't open	Copy the authorization URL `mcp-remote` prints in the terminal and open it manually
Tools return `-31001 user_not_found`	Clear cached tokens with `rm -rf ~/.mcp-auth`, then fully quit and relaunch to re-run the OAuth flow
Write tools return `-31002 access_denied`	Re-authenticate (`rm -rf ~/.mcp-auth`) with an account that has write permission

API error codes

Code	Meaning	What to do
`-28001`	Monitor limit reached	Delete unused monitors or upgrade your plan
`-28002`	Subscription limit	Interval too aggressive for your plan, or monitor type not included — loosen the interval or upgrade
`-29001`	Invalid parameters	The error message names the offending fields; fix them and retry
`-31001`	Authentication failed	See Authentication problems above
HTTP `429`	Rate limit	Back off and retry with exponential delay

For the full error reference and recovery recipes see 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

License

MIT. See LICENSE.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install UptimeRobot?

Does UptimeRobot need an API key?

What transport does UptimeRobot use?

When was UptimeRobot last checked?

Documentation

UptimeRobot for AI agents

Install

Claude Code

From the marketplace (once published)

Local clone (manual plugin install)

MCP server only (scripted)

Cursor

From the Marketplace (once published)

Local install (for development and pre-submission testing)

Codex

Local install (for development and pre-submission testing)

Other agents / direct MCP

Headless / CI (no browser)

What the plugin provides

Monitors

Monitor groups (plan-gated: monitor-groups)

Status pages (PSPs)

PSP announcements

Maintenance windows (plan-gated: maintenance-window)

Incidents

Incident comments (plan-gated: incident-comments)

Integrations & tags

No account needed

Plan requirements

Troubleshooting

Tools not showing up in Claude / Cursor

Authentication problems

API error codes

Contributing

Privacy & Terms

License

Monitor groups (plan-gated: `monitor-groups`)

Maintenance windows (plan-gated: `maintenance-window`)

Incident comments (plan-gated: `incident-comments`)