cronalert-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRONALERT_API_KEY | Yes | Your CronAlert API key, obtained from Settings > API Keys on cronalert.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_monitorsA | List all uptime monitors. Optionally filter by status (up, down, unknown) and paginate. |
| create_monitorA | Create a new uptime monitor that periodically checks a URL and alerts on failure. |
| get_monitorB | Get detailed information about a specific monitor including its current status. |
| update_monitorA | Update an existing monitor's configuration (name, URL, interval, method, etc.). |
| delete_monitorA | Permanently delete a monitor and all its check history. This cannot be undone. |
| get_check_resultsB | Get recent check results for a monitor, including response times, status codes, and uptime percentage. |
| get_monitor_incidentsB | Get incidents for a specific monitor — periods when the monitor was down. |
| list_incidentsB | List all active incidents across all monitors. |
| list_status_pagesB | List all public status pages configured for your account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.