Bring UptimeRobot data into your AI workflows.
Use MCP to list monitors, recent incidents, and integrations from your account directly in agent workflows. Write operations will follow.
Get live monitoring context in your AI tools.
List monitors and their current state
Surface which checks are up, down, or paused directly in your agent as you investigate issues.
Pull recent incidents per monitor
Pull recent incidents for any monitor to understand timing and impact fast.
See connected notification integrations
Know who gets alerted with an overview of connected notification channels.
Hosted connection with your API token
Connect to UptimeRobot’s hosted MCP endpoint using your API token without running a local server.
Agent-friendly, structured outputs
Structured responses that are easy for AI tools to parse and act on.
Connect to the hosted UptimeRobot MCP in minutes.
"uptimerobot": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.uptimerobot.com/mcp",
"--header",
"Authorization: Bearer ", // Enter your API token here.
"--header",
"X-MCP-Content-Format: true"
],
"env": {
"UPTIMEROBOT_API_TOKEN": "" // Enter your API token here.
}
},
...
1 Get your UptimeRobot API key
Create or locate your API key in your UptimeRobot dashboard (Integrations & API tab in the left sidebar).
2 Add the hosted MCP endpoint to your client
Paste the provided config snippet into your MCP client settings and replace <your-uptimerobot-api-token> with your token.
3 Restart your MCP client
Save and restart your MCP client so it can discover the tools.
4 Start querying
Use natural language to list monitors, pull recent incidents, and see connected integrations.
Note: Keep your token private. Do not commit it to source control.
Start using UptimeRobot MCP today
Connect in minutes and bring live monitoring context into your AI workflows.
What’s coming in v2.
Monitor control (write actions): Pause, resume, and update monitors. Create new monitors (HTTP, Keyword, Ping, Port, Heartbeat, DNS).
Deep incident context: Checker IPs, probe locations, traceroutes, request/response details, and related logs.
Access logs with filters: Query logs by date range, status codes, and response-time thresholds with pagination.
Response-time analytics: Time-bucketed series with averages, min/max, percentiles, and moving averages.
Monitor health stats: Up/down/paused counts and uptime percentages over a selected window.
Contacts and tags on create/update: Assign alert contacts and tags when creating or updating monitors.
Frequently asked questions.
- What can I do with MCP today?
List monitors and their current state, pull recent incidents per monitor, and see connected notification integrations. V1 is read-only.
- Can it make changes to my monitors?
Not yet. Write actions (pause/resume, create) are planned but not available in v1.
- Which AI tools does it work with?
Any MCP-compatible client. It’s client-agnostic.
- How do I set it up?
Add the hosted UptimeRobot MCP endpoint to your MCP client’s config and include your API token. Restart your client to auto-discover the tools.
- Where does my API key live? Is it secure?
You add the token to your MCP client configuration. It’s sent as a Bearer token to UptimeRobot’s hosted MCP endpoint. You can rotate or revoke the token anytime in your dashboard.
- Does MCP run locally or in the cloud?
It’s hosted by UptimeRobot. No local server is required.
Incident management
Status pages
Integrations