Skip to main content

UptimeRobot MCP Integration Guide

Use natural language to check monitor status, investigate incidents, and manage your UptimeRobot setup from any MCP-compatible AI client

Connect your AI assistant to UptimeRobot using the Model Context Protocol (MCP). Once connected, you can check monitor status, investigate incidents, and manage your monitoring setup using plain language instead of the dashboard.

MCP is an open standard that lets AI clients talk to external services. UptimeRobot's MCP server gives your AI assistant direct access to your monitors, incidents, and alert integrations.

Getting started

Step 1: Choose your authentication method

OAuth (recommended)
No setup needed. Your MCP client will prompt you to log in to UptimeRobot automatically.

API key
If your client does not support OAuth, use your UptimeRobot API key instead.

To get your API key:

  1. Log in to UptimeRobot

  2. Go to Integrations & API

  3. Copy your Main API Key. If you only need read access, copy the Read-only API Key instead.

Step 2: Configure your MCP client

The UptimeRobot MCP server runs as a remote HTTP server. Add one of the following configurations to your MCP client:

Option A — OAuth (recommended)

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

Your client will handle authentication automatically via OAuth. You can use OAuth method to add UptimeRobot MCP as a custom connector to ChatGPT, Claude.ai or Claude desktop.

Option B — API key (Bearer token)

  {
"mcpServers": {
"uptimerobot": {
"url": "https://mcp.uptimerobot.com/mcp",
"headers": {
"Authorization": "Bearer <your-api-key>"
}
}
}
}

Step 3: Verify the connection

Once configured, ask your AI assistant something like:

  • "Show me all monitors that are currently down"

  • "What's the availability of my website monitor this month?"

  • "What incidents occurred yesterday?"


What you can do

Monitors

Action

Example prompt

List all monitors

"Show me all monitors"

Filter by status

"List all monitors that are DOWN"

Get monitor details

"Show details for the homepage monitor"

Get uptime stats

"What's the uptime for the API monitor over the last 7 days?"

Get response times

"Show response times for the checkout monitor over the last 30 days"

Pause a monitor

"Pause the staging monitor for maintenance"

Resume a monitor

"Resume the staging monitor"

Update a monitor

"Update the homepage monitor to check every 5 minutes"

Create a monitor

"Create an HTTP monitor for https://api.example.com checking every 5 minutes"

Incidents

Action

Example prompt

List incidents

"List all incidents from the last 24 hours"

Filter by monitor

"Show incidents for the checkout monitor"

Get incident details

"Get full details for the latest incident on the API monitor"

Check ongoing incidents

"Are there any active incidents right now?"

Alert integrations

Action

Example prompt

List integrations

"List all my alert integrations"

Check active integrations

"Which integrations are currently active?"


Troubleshooting

"Authentication failed" or "Invalid API key"
Check for extra spaces when pasting the key. Confirm you copied the correct key from Integrations & API. If the problem persists, generate a new key.

OAuth login does not complete
Make sure your MCP client supports OAuth for remote servers. If it does not, switch to the API key method in Step 1.

My AI assistant says it has no UptimeRobot access
Confirm the configuration file was saved and the client was restarted after adding the MCP block. The URL must be exactly https://mcp.uptimerobot.com/mcp.

I can see monitors but cannot make changes
You may be using the Read-only API Key. Switch to your Main API Key if you need write access.

Some monitors or features are missing
Feature availability depends on your subscription plan. Check your current plan in the UptimeRobot dashboard.


Security

  • Your Main API Key has the same permissions as your UptimeRobot account. Use the Read-only API Key when you only need to query data.

  • API usage through MCP is subject to the same rate limits as the UptimeRobot API.


Limitations

  • Read-only API Key cannot create, update, or pause monitors.

  • Response time history is available for ranges between 1 hour and 90 days.

  • Monitor list results are paginated at 100 per page.

  • API rate limits apply. Heavy usage in a short period may result in temporary throttling.

Did this answer your question?