cronalert-mcp
This server lets an AI agent manage CronAlert uptime monitors — listing, creating, updating, deleting monitors and reviewing their check results, incidents, and status pages.
List and inspect monitors with status filtering (up/down/unknown) and pagination.
Create HTTP monitors (URL, name, method, check interval, expected status code).
Get detailed monitor info, including current status.
Update monitors (name, URL, method, interval, expected status, pause/resume).
Delete monitors permanently, including their check history.
View check results with response times, status codes, and uptime percentages.
Review incidents, either for one monitor or all active incidents across monitors.
List public status pages configured on the account.
Allows importing monitors from Better Stack into CronAlert.
Allows importing monitors from Datadog into CronAlert.
Allows importing monitors from Oh Dear into CronAlert.
Allows importing monitors from Pingdom into CronAlert.
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:
claude mcp add cronalert -e CRONALERT_API_KEY=ca_your_key -- npx -y cronalert-mcpCursor — add to .cursor/mcp.json:
{
"mcpServers": {
"cronalert": {
"command": "npx",
"args": ["-y", "cronalert-mcp"],
"env": {
"CRONALERT_API_KEY": "ca_your_api_key_here"
}
}
}
}Remote server (no install needed) — connect any MCP client to:
https://cronalert.com/mcpAuthenticate with Authorization: Bearer ca_your_key header. Supports Streamable HTTP transport.
3. Start using it
Ask your AI assistant to manage your monitors (see examples below).
4. Optional: add the Agent Skill
The server gives your agent the tools; the cronalert-uptime-monitoring skill tells it when and how to use them (monitor-type selection, heartbeat grace periods, outage triage, confirm-before-delete). Copy the folder into .claude/skills/ (Claude Code) or ~/.codex/skills/ (Codex), or install it from Agensi.
Related MCP server: DevHelm MCP Server
Available Tools
Tool | Description | Type |
| List all monitors with status and response times | Read |
| Create an HTTP, heartbeat, or TCP port monitor (heartbeats take an expected interval and grace period) | Write |
| Get details for a specific monitor | Read |
| Update settings, heartbeat interval/grace, pause/resume | Write |
| Permanently delete a monitor | Write |
| Check history with uptime % and response times | Read |
| Incidents for a specific monitor | Read |
| All active incidents across monitors | Read |
| Your public status pages | Read |
| Post a status update on an active incident | Write |
| Status updates for an incident | Read |
| Import monitors from UptimeRobot, Pingdom, Better Stack, StatusCake, Checkly, Oh Dear, Cronitor, Healthchecks.io, Dead Man's Snitch, Datadog, CronAlert JSON, or CSV | Write |
Security & permissions
Approvals in MCP clients are client-side: write tools carry destructiveHint: true, so Claude Code / Desktop / Cursor prompt before running them. CronAlert adds two server-side boundaries so the client prompt isn't the only gate:
Read-only API keys. A read-only key is rejected on every write endpoint (create/update/delete/import) with a 403 — enforced by the server, regardless of the client. Hand agents a read-only key and destructive tools simply cannot succeed. This is the strongest boundary and the recommended default.
Confirmation tokens for deletes. If a read-write key has "require confirmation" enabled,
delete_monitorfirst returns a preview plus a short-lived, resource-boundconfirmTokeninstead of deleting. The agent must calldelete_monitoragain with that token in theconfirmargument. This prevents a single stray or prompt-injected call from destroying data and gives the server an auditable, explicit second step.
The API key is scoped to a single team, so the blast radius of any key is that team's resources.
Examples
Example 1: Create a monitor and check its status
User prompt: "Create a monitor for https://api.example.com/health that checks every minute, then show me its details."
What happens:
The AI calls
create_monitorwithname: "API Health",url: "https://api.example.com/health",checkInterval: 60CronAlert creates the monitor and returns its ID
The AI calls
get_monitorwith the new ID to show the details
Expected output:
{
"id": "abc123",
"name": "API Health",
"url": "https://api.example.com/health",
"method": "GET",
"checkInterval": 60,
"lastStatus": "unknown",
"createdAt": "2026-03-08T12:00:00Z"
}Example 2: Check uptime and respond to incidents
User prompt: "Are any of my monitors down? If so, show me the error details."
What happens:
The AI calls
list_incidentsto check for active incidentsIf incidents exist, it calls
get_monitorfor each affected monitorIt calls
get_check_resultsto get the recent error details
Expected output (no incidents):
{
"data": [],
"message": "No active incidents"
}Expected output (with incident):
{
"data": [
{
"id": "inc_xyz",
"monitorId": "abc123",
"cause": "Expected status 200, got 503",
"startedAt": "2026-03-08T11:45:00Z"
}
]
}Example 3: List monitors and pause one for maintenance
User prompt: "List all my monitors, then pause the staging one."
What happens:
The AI calls
list_monitorsto get all monitorsIt identifies the staging monitor by name
It calls
update_monitorwithid: "staging_id"andpaused: true
Expected output:
{
"id": "staging_id",
"name": "Staging Server",
"isPaused": true,
"lastStatus": "up"
}Example 4: Heartbeat for a nightly backup (v1.5.0+)
User prompt: "Create a heartbeat monitor called Nightly DB backup that expects a ping every 24 hours with a 2-hour grace period, and give me the URL to add to the cron job."
What happens:
The AI calls
create_monitorwithtype: "heartbeat",name: "Nightly DB backup",checkInterval: 86400,gracePeriod: 7200CronAlert returns the monitor including its unique ping
urlThe AI shows the URL to append to the job, e.g.
pg_dump ... && curl -fsS <url>
checkInterval is the expected seconds between pings (plan minimum, 60 on Pro+, up to 604800). gracePeriod is optional; it defaults to the interval capped at one hour. For http and tcp monitors checkInterval is ignored and set from your plan.
Requirements
Node.js 18+
A CronAlert account (free tier works)
An API key from Settings > API Keys
Privacy Policy
This MCP server connects to the CronAlert API (cronalert.com/api/v1/) using your API key. It transmits:
Monitor configuration (names, URLs, check intervals) when creating or updating monitors
API key for authentication on every request
Data is processed by CronAlert's servers on Cloudflare's infrastructure. No data is stored locally by the MCP server itself. See our full Privacy Policy for details on data collection, retention, and your rights.
Support
Website: cronalert.com
Email: support@cronalert.com
Issues: GitHub Issues
License
MIT
Available Tools
9 toolscreate_monitorADestructive
Create a new uptime monitor that periodically checks a URL and alerts on failure.
Inputs: name (required), url (required), checkInterval, method, +1 more.
delete_monitorADestructive
Permanently delete a monitor and all its check history. This cannot be undone.
Inputs: id (required).
get_check_resultsBRead-only
Get recent check results for a monitor, including response times, status codes, and uptime percentage.
Inputs: id (required), page, limit.
get_monitorBRead-only
Get detailed information about a specific monitor including its current status.
Inputs: id (required).
get_monitor_incidentsBRead-only
Get incidents for a specific monitor — periods when the monitor was down.
Inputs: id (required), page, limit.
list_incidentsBRead-only
List all active incidents across all monitors.
Inputs: no named parameters.
list_monitorsARead-only
List all uptime monitors. Optionally filter by status (up, down, unknown) and paginate.
Inputs: page, limit, status.
list_status_pagesBRead-only
List all public status pages configured for your account.
Inputs: no named parameters.
update_monitorADestructive
Update an existing monitor's configuration (name, URL, interval, method, etc.).
Inputs: id (required), name, url, checkInterval, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized around specific resources (monitors, incidents, status pages) and actions (create, delete, get, list, update), making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (e.g., create_monitor, list_incidents, update_monitor). The naming is uniform throughout, using snake_case and clear, descriptive verbs that align with the action each tool performs.
With 9 tools, the server is well-scoped for uptime monitoring and alerting. Each tool serves a distinct and necessary function, covering core operations like CRUD for monitors, incident management, and status page listing, without being overly sparse or bloated.
The tool surface provides complete CRUD/lifecycle coverage for the uptime monitoring domain. It includes creation, retrieval, updating, and deletion of monitors, along with incident tracking and status page management, leaving no obvious gaps for agent workflows.
Related MCP Connectors
MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents.
Uptime, SSL, DNS and domain monitoring you can talk to from Claude or any MCP client.
AI-powered incident management and server monitoring via MCP.
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. This MCP server lets your agent create, update, pause and delete checks, build dashboards and publish them as status pages, manage notification groups, and read incidents with their causes, uptime, run history and latency. Pause, delete and unpublish stay off until you turn them on. Browser sign-in, no API key needed.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceMCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.18 npmMIT
DevHelm MCP Serverofficial
AlicenseCqualityAmaintenanceMCP server for uptime monitoring, incidents, alerting, and dependency status.12954 PyPI1MIT
Drumbeats MCPofficial
AlicenseAqualityBmaintenanceMCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.1966 npm2Apache 2.0
uptimepageofficial
AlicenseNot gradedqualityBmaintenanceMCP server for Uptimepage uptime monitoring. An LLM client can read your monitors and incidents, run a check on demand, and post incident updates. Writes need an OAuth login and a scoped token, and each one is logged.60AGPL 3.0