--- title: "UptimeRobot MCP server for AI agents - actionlake" description: "Give Claude 64 UptimeRobot actions through one MCP server: monitors, status page announcements, alert contacts. 100,000 calls a month free, no card." canonical: https://actionlake.com/connectors/uptimerobot updated: 2026-10-22 --- Connectors · MSP & PSA # UptimeRobot MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to UptimeRobot and the rest of your systems. It gives your agent 64 UptimeRobot actions (30 reads, 24 writes and 10 that wait for a confirmation) and holds the UptimeRobot credential itself, so the agent never does. It paces UptimeRobot's limits and records every call. [Connect UptimeRobot free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "uptimerobot.monitors.list", intent: "check which UptimeRobot account is connected" } # List monitors · read · 1 upstream call ``` - 64 actions in one signed file - 30 read look, never change - 24 write create and update - 10 wait for a yes destructive, confirmed first Set up ## Connect UptimeRobot in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect UptimeRobot. Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_key` UptimeRobot API key ``` account { op: "connections.requirements", service: "uptimerobot" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "uptimerobot.monitors.list" } # list monitors · read · 1 upstream call check { action: "uptimerobot.monitors.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` UptimeRobot at a glance **Sign-in** Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_key` **Limits we pace to** 10 calls a minute, per connection **API covered** UptimeRobot API v3 (3.0)`api.uptimerobot.com/v3` **Built from** UptimeRobot's documentation, read 22 October 2026[cdn.uptimerobot.com](https://cdn.uptimerobot.com/api/openapi.yaml) [uptimerobot.com](https://uptimerobot.com/api/v3/) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 30 of 30 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 3, so ask can line UptimeRobot up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in UptimeRobot. 64 actions in 14 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **30** read look, never change - **24** write create and update - **10** destructive wait for a confirmation 1. ### Monitors 17 8 read · 7 write · 2 destructive List monitors · Create a monitor · Get a monitor by ID · Update a monitor 2. ### Status page announcements 7 2 read · 4 write · 1 destructive Create an announcement · List announcements · Get an announcement by ID · Pin an announcement 3. ### Alert contacts 5 2 read · 2 write · 1 destructive Create a personal alert contact · List personal alert contacts · Get a personal alert contact by ID · Update a personal alert contact 4. ### Integrations 5 2 read · 2 write · 1 destructive Create an Integration · List Integrations · Get an integration by ID · Update an Integration 5. ### Maintenance windows 5 2 read · 2 write · 1 destructive Create a maintenance window · List maintenance windows · Get a maintenance window by ID · Update a maintenance window 6. ### Monitor groups 5 2 read · 2 write · 1 destructive Create a monitor group · List monitor groups · Get a monitor group by ID · Update a monitor group 7. ### Status pages 5 2 read · 2 write · 1 destructive Create a PSP · List PSPs · Get a PSP by ID · Update a PSP 8. ### Incident comments 4 1 read · 2 write · 1 destructive Create incident comment · List incident comments · Update an incident comment · Delete incident comment **6 more areas · 11 actions** - User **3** - Incidents **2** - Storm protection **2** - Tags **2** - Incident activity log **1** - Incident alerts **1** Top actions ## The UptimeRobot API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 13 of UptimeRobot's 13 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `uptimerobot.monitors.list` List monitors | List monitors. | read | `monitoring.monitor.list` 32 connectors | | `uptimerobot.user.me` Get current user | Get current user. | read | `identity.current_user.get` 307 connectors | | `uptimerobot.incidents.list` List incidents | List incidents. | read | `monitoring.incident.list` 19 connectors | | `uptimerobot.monitors.create` Create a monitor | Create a monitor. | write | `monitoring.monitor.create` 27 connectors | | `uptimerobot.incidents.get` Get an incident by ID | Get an incident by ID. | read | `monitoring.incident.get` 20 connectors | | `uptimerobot.monitors.delete` Delete a monitor | Delete a monitor. | destructive | `monitoring.monitor.delete` 31 connectors | | `uptimerobot.incident_comments.create` Create incident comment | Create incident comment. | write | `monitoring.incident_note.create` 12 connectors | | `uptimerobot.incident_comments.list` List incident comments | List incident comments. | read | `monitoring.incident_note.list` 11 connectors | | `uptimerobot.tags.list` List user tags | List user tags. | read | this connector | | `uptimerobot.integrations.list` List Integrations | List Integrations. | read | this connector | | `uptimerobot.status_pages.list` List PSPs | List PSPs. | read | this connector | | `uptimerobot.integrations.create` Create an Integration | Create an Integration. | write | this connector | Try it ## Prompts to paste into Claude. Each one names the UptimeRobot actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which UptimeRobot incidents are open, and how long has each been open? calls `uptimerobot.incidents.list` 2. Write write Create a monitor in UptimeRobot. Show me exactly what you will send before you save it. calls `uptimerobot.monitors.create` Governance for UptimeRobot ## Destructive actions wait for a yes. 10 UptimeRobot actions are destructive. These are all of them: - Delete a monitor `uptimerobot.monitors.delete` - Delete incident comment `uptimerobot.incident_comments.delete` - Delete a tag `uptimerobot.tags.delete` - Delete an Integration `uptimerobot.integrations.delete` - Delete a PSP `uptimerobot.status_pages.delete` - Reset stats for a monitor `uptimerobot.monitors.reset_stats` - Delete a personal alert contact `uptimerobot.alert_contacts.delete` - Delete a monitor group `uptimerobot.monitor_groups.delete` - Delete a maintenance window `uptimerobot.maintenance_windows.delete` - Delete an announcement `uptimerobot.status_page_announcements.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do uptimerobot.monitors.delete confirm_policy: **human** Delete a monitor? **intent:** the user asked me to delete a monitor run suspended · waiting for a named person · key _uptimerobot-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "uptimerobot-agent", allowed_actions: ["uptimerobot.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "uptimerobot.monitors.delete", approver: "lead@example.com" }, { match: "uptimerobot.incident_comments.delete", approver: "lead@example.com" }, { match: "uptimerobot.tags.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to UptimeRobot only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What UptimeRobot costs on actionlake. Every UptimeRobot action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call UptimeRobot refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 64 UptimeRobot actions - 64 actions page each page of a long list is one call - 30 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every UptimeRobot action. 64 actions by area: the id your agent calls, what it does, and its effect. **Monitors 17** - `uptimerobot.monitors.bulk_pause` Pause monitors by group and/or tag write - `uptimerobot.monitors.bulk_start` Start monitors by group and/or tag write - `uptimerobot.monitors.bulk_update` Update monitors by group and/or tag write - `uptimerobot.monitors.create` Create a monitor write - `uptimerobot.monitors.delete` Delete a monitor destructive - `uptimerobot.monitors.get` Get a monitor by ID read - `uptimerobot.monitors.get_account_uptime_stats` Get aggregated uptime statistics read - `uptimerobot.monitors.get_dependency_status` Get the current status of a dependency monitor read - `uptimerobot.monitors.get_response_time_stats` Get monitor response time statistics read - `uptimerobot.monitors.get_response_time_stats_by_region` Get monitor response time statistics by region read - `uptimerobot.monitors.get_uptime_stats` Get monitor uptime statistics read - `uptimerobot.monitors.list` List monitors read - `uptimerobot.monitors.list_dependency_incidents` Get the incident history of a dependency monitor read - `uptimerobot.monitors.pause` Pause a monitor write - `uptimerobot.monitors.reset_stats` Reset stats for a monitor destructive - `uptimerobot.monitors.start` Start a monitor write - `uptimerobot.monitors.update` Update a monitor write **Status page announcements 7** - `uptimerobot.status_page_announcements.create` Create an announcement write - `uptimerobot.status_page_announcements.delete` Delete an announcement destructive - `uptimerobot.status_page_announcements.get` Get an announcement by ID read - `uptimerobot.status_page_announcements.list` List announcements read - `uptimerobot.status_page_announcements.pin` Pin an announcement write - `uptimerobot.status_page_announcements.unpin` Unpin an announcement write - `uptimerobot.status_page_announcements.update` Update an announcement write **Alert contacts 5** - `uptimerobot.alert_contacts.create` Create a personal alert contact write - `uptimerobot.alert_contacts.delete` Delete a personal alert contact destructive - `uptimerobot.alert_contacts.get` Get a personal alert contact by ID read - `uptimerobot.alert_contacts.list` List personal alert contacts read - `uptimerobot.alert_contacts.update` Update a personal alert contact write **Integrations 5** - `uptimerobot.integrations.create` Create an Integration write - `uptimerobot.integrations.delete` Delete an Integration destructive - `uptimerobot.integrations.get` Get an integration by ID read - `uptimerobot.integrations.list` List Integrations read - `uptimerobot.integrations.update` Update an Integration write **Maintenance windows 5** - `uptimerobot.maintenance_windows.create` Create a maintenance window write - `uptimerobot.maintenance_windows.delete` Delete a maintenance window destructive - `uptimerobot.maintenance_windows.get` Get a maintenance window by ID read - `uptimerobot.maintenance_windows.list` List maintenance windows read - `uptimerobot.maintenance_windows.update` Update a maintenance window write **Monitor groups 5** - `uptimerobot.monitor_groups.create` Create a monitor group write - `uptimerobot.monitor_groups.delete` Delete a monitor group destructive - `uptimerobot.monitor_groups.get` Get a monitor group by ID read - `uptimerobot.monitor_groups.list` List monitor groups read - `uptimerobot.monitor_groups.update` Update a monitor group write **Status pages 5** - `uptimerobot.status_pages.create` Create a PSP write - `uptimerobot.status_pages.delete` Delete a PSP destructive - `uptimerobot.status_pages.get` Get a PSP by ID read - `uptimerobot.status_pages.list` List PSPs read - `uptimerobot.status_pages.update` Update a PSP write **Incident comments 4** - `uptimerobot.incident_comments.create` Create incident comment write - `uptimerobot.incident_comments.delete` Delete incident comment destructive - `uptimerobot.incident_comments.list` List incident comments read - `uptimerobot.incident_comments.update` Update an incident comment write **User 3** - `uptimerobot.user.list_alert_contacts` Get alert contacts read - `uptimerobot.user.list_all_alert_contacts` Get all alert contacts read - `uptimerobot.user.me` Get current user read **Incidents 2** - `uptimerobot.incidents.get` Get an incident by ID read - `uptimerobot.incidents.list` List incidents read **Storm protection 2** - `uptimerobot.storm_protection.get` Get storm protection settings read - `uptimerobot.storm_protection.update` Update storm protection settings write **Tags 2** - `uptimerobot.tags.delete` Delete a tag destructive - `uptimerobot.tags.list` List user tags read **Incident activity log 1** - `uptimerobot.incident_activity_log.list` Get incident activity log read **Incident alerts 1** - `uptimerobot.incident_alerts.list` Get incident sent alerts read Questions ## The UptimeRobot MCP server, answered. **Is there an UptimeRobot MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 64 UptimeRobot actions across monitors, status page announcements, alert contacts and integrations, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by UptimeRobot. **What do I need to connect UptimeRobot?** UptimeRobot API key. The free call account { op: "connections.requirements", service: "uptimerobot" } lists exactly what to paste. **Can an AI agent delete or change things in UptimeRobot?** Only if its key allows it, and only with an explicit confirmation. 10 UptimeRobot actions are destructive, including delete a monitor, delete incident comment and delete a tag. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my UptimeRobot API limit?** actionlake paces every call to the limits in the UptimeRobot service file: 10 calls a minute per connection. Repeated reads are answered from cache (30 UptimeRobot actions can be), which never reaches UptimeRobot. **What does an UptimeRobot action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (64 UptimeRobot actions page). Cache hits, searches, dry runs and calls UptimeRobot refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which UptimeRobot API does it cover?** The UptimeRobot API v3 (3.0) at api.uptimerobot.com/v3. It is built from UptimeRobot's documentation as read on 22 October 2026. 64 actions in 14 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my UptimeRobot data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your UptimeRobot credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like UptimeRobot Shares the most action names with - [DigitalOcean 6](https://actionlake.com/connectors/digitalocean) - [Logz.io 5](https://actionlake.com/connectors/logz-io) - [Azure Monitor 4](https://actionlake.com/connectors/azure-monitor) - [Site24x7 4](https://actionlake.com/connectors/site24x7) - [Microsoft 365 Service Health and Message Center 3](https://actionlake.com/connectors/microsoft-365-service-health-and-message-center) - [Acronis Cyber Protect Cloud 3](https://actionlake.com/connectors/acronis-cyber-protect-cloud) Joins with, on shared entities - [ilert 3](https://actionlake.com/connectors/ilert) - [Dynatrace 2](https://actionlake.com/connectors/dynatrace) - [FireHydrant 2](https://actionlake.com/connectors/firehydrant) - [Better Stack Uptime 2](https://actionlake.com/connectors/better-stack-uptime) - [Splunk SOAR 2](https://actionlake.com/connectors/splunk-soar) - [Rubrik Security Cloud 1](https://actionlake.com/connectors/rubrik-security-cloud) Browse - [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by UptimeRobot; the name is the vendor's own. Counts are from the UptimeRobot service file, version 1.0.0. ## Give your agent UptimeRobot today. [Connect UptimeRobot free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/uptimerobot More: https://actionlake.com/llms.txt