CronAlert
@jaredhobbs
Manage CronAlert uptime monitors, check results, and incidents from any MCP client.
Overview
What is CronAlert?
CronAlert is an MCP server for CronAlert uptime monitoring. It lets you manage monitors, check results, and incidents from Claude, Cursor, Windsurf, or any MCP-compatible AI client.
How to use CronAlert?
Get an API key from your CronAlert account settings. Add the server to your MCP client configuration (e.g., Claude Desktop, Claude Code, Cursor, or via the remote endpoint). Then ask your AI assistant to manage your monitors.
Key features of CronAlert
- List all monitors with status and response times
- Create new HTTP monitors
- Get detailed monitor information
- Update settings, pause, or resume monitors
- Permanently delete monitors
- View check history with uptime percentage and response times
- Retrieve incidents for a specific monitor
- List all active incidents across monitors
- Display your public status pages
Use cases of CronAlert
- Create a monitor for a health endpoint and immediately check its status
- Check if any monitors are down and get error details
- List all monitors, then pause a staging monitor for maintenance
FAQ from CronAlert
What do I need to use CronAlert?
Node.js 18+, a CronAlert account (free tier works), and an API key from Settings > API Keys.
Can I connect to CronAlert without installing anything?
Yes, connect any MCP client to https://cronalert.com/mcp and authenticate with an Authorization: Bearer ca_your_key header. It supports Streamable HTTP transport.
What data does the CronAlert MCP server transmit?
Monitor configuration (names, URLs, check intervals) and your API key for authentication on every request.
Where is my data stored?
Data is processed by CronAlert's servers on Cloudflare's infrastructure. No data is stored locally by the MCP server itself.
How can I get support or report issues?
Email [email protected], visit cronalert.com, or open an issue on the GitHub Issues page.
