Manage CronAlert uptime monitors, check results, and incidents from any MCP client.
Most developer tooling work still happens through a UI a human drives. Cronalert MCP server moves it into the conversation instead. Manage CronAlert uptime monitors, check results, and incidents from any MCP client.
MCP server for CronAlert uptime monitoring. Manage your monitors, check results, and incidents from Claude, Cursor, Windsurf, or any MCP-compatible AI client.
The server publishes 10 tools. What each one is for:
Read-only — the agent can list and read monitors, check results, and incidents but cannot create, update, or delete anything. Recommended for most agentlist_monitors — List all monitors with status and response timescreate_monitor — Create a new HTTP monitorget_monitor — Get details for a specific monitorupdate_monitor — Update settings, pause/resumedelete_monitor — Permanently delete a monitorget_check_results — Check history with uptime % and response timesget_monitor_incidents — Incidents for a specific monitorlist_incidents — All active incidents across monitorslist_status_pages — Your public status pagesConfiguration is passed through the environment: CRONALERT_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as cronalert-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cronalert's toolset — Read-only, list_monitors, create_monitor and 7 more — is a fair guide to whether it matches your workflow. It is maintained by jaredhobbs; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| 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. |
| list_monitors | List all monitors with status and response times |
| create_monitor | Create a new HTTP monitor |
| get_monitor | Get details for a specific monitor |
| update_monitor | Update settings, pause/resume |
| delete_monitor | Permanently delete a monitor |
| get_check_results | Check history with uptime % and response times |
| get_monitor_incidents | Incidents for a specific monitor |
| list_incidents | All active incidents across monitors |
| list_status_pages | Your public status pages |
{
"mcpServers": {
"cronalert": {
"command": "npx",
"args": ["-y", "cronalert-mcp"],
"env": {
"CRONALERT_API_KEY": "ca_your_api_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CRONALERT_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.