UptimeRobot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPTIMEROBOT_API_KEY | Yes | Your UptimeRobot API key from the dashboard under Integrations & API → API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_monitorsA | Get all monitors with optional filtering. |
| get_monitorA | Get a single monitor by ID with detailed information. |
| create_monitorB | Create a new monitor. |
| edit_monitorA | Edit an existing monitor. Only provided fields are updated. |
| delete_monitorA | Permanently delete a monitor by ID. |
| reset_monitorA | Reset a monitor, clearing all historical statistics and logs. |
| get_monitor_logsA | Get up/down event logs for a specific monitor. |
| get_account_detailsA | Get UptimeRobot account details. Returns account information including email, monitor limits, and counts of up, down, and paused monitors. |
| get_alert_contactsC | Get all alert contacts. |
| create_alert_contactC | Create a new alert contact. |
| edit_alert_contactC | Edit an existing alert contact. |
| delete_alert_contactA | Delete an alert contact by ID. |
| get_mwindowsB | Get all maintenance windows. |
| create_mwindowC | Create a new maintenance window. |
| edit_mwindowB | Edit an existing maintenance window. |
| delete_mwindowA | Delete a maintenance window by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool maps to a distinct resource and action, such as monitors, alert contacts, and maintenance windows. The separation between list, get, create, edit, delete, and specialized operations like reset or logs is clear.
All tools follow a consistent verb_noun pattern, using plural nouns for list operations and singular nouns for single-item operations. The naming is uniform across all three resource types.
At 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for the domain. Each tool addresses a meaningful operation, and the count feels justified rather than bloated.
The tool surface covers full CRUD for monitors, alert contacts, and maintenance windows, plus useful extras like monitor logs and account details. Minor gaps exist (e.g., single alert contact retrieval, monitor pause/resume), but core workflows are complete.