UptimeRobot MCP. Manage all web health checks and alerts from your chat.

UptimeRobot MCP Server: Web Health Status Monitoring

Forget logging into a dashboard just to check if your site's up. This server lets you manage every aspect of your web uptime checks—from setting up new endpoints to controlling who gets alerted when things go sideways—all through your AI client. You get instant visibility on service health and historical data without lifting a finger to open a browser.

Checking Your Site Status

To see what's going on right now, you use list_monitors. This tool pulls the current pass/fail status for every single uptime monitor you've configured. It shows you the up ratio and the response times immediately, so you know exactly if everything's humming along or if something tripped a wire. When you need deep dives on just one specific service, get_monitor_details pulls the full configuration details for that single monitor.

If you suspect some settings are stale, remember you can use update_uptime_monitor to modify things like the URL or the check type on an existing endpoint.

Setting Up and Tearing Down Checks

You gotta keep your monitoring endpoints current. You run create_uptime_monitor when you need to set up a brand-new check, whether it's an HTTP status code test or a simple Ping request for a new URL. The parameters are straightforward: tell the agent what site and how often, and it handles the rest.

When a service is retired, you use delete_uptime_monitor to remove that monitoring check entirely. This action is permanent, so be sure of what you're deleting.

Controlling Alert Recipients

When things fail, someone needs to know. You manage those people using the alert tools. First, run list_alert_contacts to get a clean list of every contact—Email, Slack, or Webhook—that currently gets paged when an outage happens. If you need to add a new notification channel, use create_alert_contact; this adds either a new email address or a dedicated Slack integration as a target for system downtime alerts.

When a team member changes roles or a contact point is abandoned, you run delete_alert_contact to permanently wipe that notification target from the system.

Managing Account Limits and History

It's smart to know your limits before things get hairy. You check your capacity by calling get_account_info. This gives you a clear picture of your remaining monitor slots and overall subscription usage, so you never hit a paywall surprise. For analyzing performance trends, you can fetch raw data arrays for up ratios or use reset_monitor_logs to clear out old historical statistics for a specific service monitor when you need a clean slate for analysis.

How It Works in Practice

When you tell your agent, 'Check the status of the main checkout page and tell me if we're over our limit,' the system knows exactly what to do. It runs list_monitors first. Then, it uses the data from get_account_info to check the usage metrics against its known limits. If you then say, 'Hey, add my manager's email for alerts,' the agent calls create_alert_contact.

You don't deal with API keys or dashboards; your AI client just runs these tools and gives you plain text back. It’s direct, fast, and keeps your operational data right where you are.