
Cronalert
Connects to the CronAlert uptime monitoring API and exposes tools for managing HTTP monitors, checking uptime history, and querying incidents. You can create monitors with custom intervals, pause them for maintenance windows, pull check results with response times and uptime percentages, and list active incidents across your fleet. Works with your CronAlert API key from their dashboard. Useful when you want to manage monitoring alongside other infrastructure tasks in your AI workflow, or when an assistant needs to check service health and respond to outages without leaving the conversation.
- tools
- 12
- transport
- STDIO
- last updated
- Sep 25, 2026
Tools
12 toolsPublic tool metadata for what this MCP can expose to an agent.
list_monitorsList all monitors with status and response times
List all monitors with status and response times
No parameter schema in public metadata yet.
create_monitorCreate an HTTP, heartbeat, or TCP port monitor (heartbeats take an expected interval and grace period)
Create an HTTP, heartbeat, or TCP port monitor (heartbeats take an expected interval and grace period)
No parameter schema in public metadata yet.
get_monitorGet details for a specific monitor
Get details for a specific monitor
No parameter schema in public metadata yet.
update_monitorUpdate settings, heartbeat interval/grace, pause/resume
Update settings, heartbeat interval/grace, pause/resume
No parameter schema in public metadata yet.
delete_monitorPermanently delete a monitor
Permanently delete a monitor
No parameter schema in public metadata yet.
get_check_resultsCheck history with uptime % and response times
Check history with uptime % and response times
No parameter schema in public metadata yet.
get_monitor_incidentsIncidents for a specific monitor
Incidents for a specific monitor
No parameter schema in public metadata yet.
list_incidentsAll active incidents across monitors
All active incidents across monitors
No parameter schema in public metadata yet.
list_status_pagesYour public status pages
Your public status pages
No parameter schema in public metadata yet.
add_incident_updatePost a status update on an active incident
Post a status update on an active incident
No parameter schema in public metadata yet.
get_incident_updatesStatus updates for an incident
Status updates for an incident
No parameter schema in public metadata yet.
import_monitorsImport monitors from UptimeRobot, Pingdom, Better Stack, StatusCake, Checkly, Oh Dear, Cronitor, Healthchecks.io, Dead Man's Snitch, Datadog, CronAlert JSON, or CSV
Import monitors from UptimeRobot, Pingdom, Better Stack, StatusCake, Checkly, Oh Dear, Cronitor, Healthchecks.io, Dead Man's Snitch, Datadog, CronAlert JSON, or CSV
No parameter schema in public metadata yet.
Sponsors
Readme
cronalert-mcp
MCP server for CronAlert uptime monitoring. Manage your monitors, check results, and incidents from Claude, Cursor, Windsurf, or any MCP-compatible AI client.
Quick Start
1. Get your API key
Sign up at cronalert.com and create an API key in Settings > API Keys.
When creating the key, choose a scope:
- Read-only — the agent can list and read monitors, check results, and incidents but cannot create, update, or delete anything. Recommended for most agent setups.
- Read & write — full access, including destructive tools. Optionally enable "require confirmation" so deletes need a server-issued confirmation token (see Security & permissions).
2. Add to your MCP client
Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"cronalert": {
"command": "npx",
"args": ["-y", "cronalert-mcp"],
"env": {
"CRONALERT_API_KEY": "ca_your_api_key_here"
}
}
}
}
Claude Code — run:
Details
- Repository
- github.com/jaredhobbs/cronalert-mcp
- Category
- Monitoring & Observability
- Package
cronalert-mcp- Transport
- STDIO
- Registry
- MCP registry, active