UptimeRobot logoMCP server · Engineering and operations

UptimeRobot MCP server

UptimeRobot in any MCP client, through Memtro: UptimeRobot does not publish this server. Memtro's UptimeRobot connector reads UptimeRobot through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

UptimeRobot uptime monitoring: monitors and their status, incidents (downtime, slow responses) with comments, uptime statistics for a period, maintenance windows, status pages and alert contacts. Can, when asked, create, edit, pause, resume, reset or delete a monitor, schedule or delete a maintenance window, post or edit a status page announcement, and add or edit an internal incident comment.

Reads

  • uptimerobot_list_monitorsUptimeRobot monitors: name, URL, type, status (UP, DOWN, PAUSED…), check interval and tags.
  • uptimerobot_get_monitorOne UptimeRobot monitor by id, with its configuration and current status.
  • uptimerobot_list_incidentsUptimeRobot incidents (downtime, slow response, visual change): monitor, cause, when it started and was resolved.
  • uptimerobot_get_incidentOne UptimeRobot incident by id, with up to 20 of its comments.
  • uptimerobot_get_uptime_statsUptime statistics across monitors for a period (last day, week, month, 30 days, year or all time).
  • uptimerobot_list_maintenance_windowsScheduled maintenance windows, during which monitors are paused.
  • uptimerobot_list_status_pagesPublic status pages: name, status, custom domain and the monitors shown.
  • uptimerobot_list_alert_contactsWho or what is alerted when a monitor goes down: email, SMS, Slack and other alert contacts.

Acts, when you ask

These change something in UptimeRobot. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • uptimerobot_create_incident_commentAdd a new internal comment to an UptimeRobot incident (e.g. what was found or done).
  • uptimerobot_update_incident_commentReplace the text of an internal comment on an UptimeRobot incident.
  • uptimerobot_pause_monitorPause an UptimeRobot monitor: it stops being checked and raises no alerts until resumed.
  • uptimerobot_resume_monitorResume (start) a paused UptimeRobot monitor so it is checked and alerts again.
  • uptimerobot_create_monitorCreate an UptimeRobot monitor (HTTP, KEYWORD, PING, PORT or HEARTBEAT) that starts checking at once and counts against the plan's monitor limit.
  • uptimerobot_update_monitorChange an UptimeRobot monitor: its name, URL, check interval, timeout, port, grace period, alert contacts (changes who is paged), tags…
  • uptimerobot_delete_monitorPermanently delete an UptimeRobot monitor and its history; it cannot be undone (pause it instead to stop checks).
  • uptimerobot_reset_monitor_statsPermanently reset an UptimeRobot monitor's statistics, clearing its incident and alert history.
  • uptimerobot_create_maintenance_windowSchedule an UptimeRobot maintenance window during which the listed monitors do not alert.
  • uptimerobot_delete_maintenance_windowDelete an UptimeRobot maintenance window; its monitors alert normally again.
  • uptimerobot_create_status_page_announcementPost an announcement on an UptimeRobot public status page.
  • uptimerobot_update_status_page_announcementEdit, publish or archive an announcement on an UptimeRobot status page.

Connect it

First connect UptimeRobot on Dashboard → Connections, then add Memtro to your client once. The UptimeRobot tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared UptimeRobot connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which monitors are down right now?
  • › When was the website last down, and for how long?
  • › What was our uptime last month across all monitors?
  • › Pause the staging monitor until Monday
  • › Schedule a maintenance window for the API monitors tonight from 22:00 to 23:00

Questions

Is this an official UptimeRobot MCP server?
No. It is Memtro's MCP server with Memtro's UptimeRobot connector behind it: the connector reads UptimeRobot through its API with the credentials you connect on Dashboard → Connections, and UptimeRobot publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in UptimeRobot?
Only when you ask, and only what it has been granted: add an internal comment to an incident; edit an internal incident comment; pause an UptimeRobot monitor; resume a paused UptimeRobot monitor; create an UptimeRobot monitor; edit an UptimeRobot monitor; delete an UptimeRobot monitor (permanent, with its history); reset an UptimeRobot monitor's statistics (permanent); schedule an UptimeRobot maintenance window; delete an UptimeRobot maintenance window; post an announcement on an UptimeRobot status page (public when published); edit, publish or archive a status page announcement. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time