Schema | UptimeRobot MCP Server

UptimeRobot MCP Server

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

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }
`logging`	{}
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`extensions`	{ "io.modelcontextprotocol/ui": {} }
`experimental`	{}

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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/84emllc/uptimerobot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server