watchcron-mcp
OfficialLists the notification channels configured in WatchCron, including Slack channels alongside email and webhooks, so an agent can see where monitor alerts are delivered.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@watchcron-mcp Create a monitor for my daily backup that runs every 24 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
watchcron-mcp
Monitor your cron jobs and scheduled tasks from AI agents. MCP server for WatchCron.
Features
List all cron job monitors and their current status
Create new monitors with simple interval or cron expression schedules
Get the ping URL to add to your crontab or task scheduler
View ping history and incident timeline
Pause and resume monitors
Update monitor settings (schedule, grace period, tags)
Delete monitors you no longer need
List notification channels (email, Slack, webhook)
Related MCP server: healthchecks-io-mcp
Quick Start
1. Get your API key
Sign up and generate an API key at watchcron.com.
2. Configure your AI client
Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"watchcron": {
"command": "npx",
"args": ["-y", "watchcron-mcp"],
"env": {
"WATCHCRON_API_KEY": "your_api_key_here"
}
}
}
}Claude Code
claude mcp add watchcron \
npx -y watchcron-mcp \
-e WATCHCRON_API_KEY=your_api_key_hereCursor
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"watchcron": {
"command": "npx",
"args": ["-y", "watchcron-mcp"],
"env": {
"WATCHCRON_API_KEY": "your_api_key_here"
}
}
}
}Windsurf
Add to your Windsurf MCP configuration with the same npx -y watchcron-mcp command and set the WATCHCRON_API_KEY environment variable.
Available Tools
list_monitors
List all cron job monitors in your project. Optionally filter by tag.
Parameter | Type | Description |
| string | Filter monitors by tag (optional) |
get_monitor
Get detailed info about a specific monitor.
Parameter | Type | Description |
| string | Monitor UUID |
create_monitor
Create a new cron job monitor. Returns the ping URL to add to your cron job.
Parameter | Type | Default | Description |
| string | required | Monitor name (e.g. "Daily backup") |
| string | — | Optional description |
|
| required | Fixed interval or cron expression |
| number | — | Interval in seconds (for simple schedule, min 60) |
| string | — | Cron expression (for cron schedule) |
| string | UTC | Timezone for schedule |
| number | — | Grace period before alerting |
| string[] | — | Tags for organizing |
update_monitor
Update an existing monitor's settings.
Parameter | Type | Description |
| string | Monitor UUID |
| string | New name |
| string | New description |
|
| New schedule type |
| number | New interval |
| string | New cron expression |
| string | New timezone |
| number | New grace period |
| string[] | New tags |
delete_monitor
Permanently delete a monitor.
Parameter | Type | Description |
| string | Monitor UUID |
pause_monitor
Pause or resume a monitor.
Parameter | Type | Default | Description |
| string | required | Monitor UUID |
| boolean | true | true to pause, false to resume |
get_pings
Get recent ping history for a monitor.
Parameter | Type | Default | Description |
| string | required | Monitor UUID |
| number | 10 | Number of pings to return (1-100) |
get_incidents
Get status change history (down/up transitions).
Parameter | Type | Default | Description |
| string | required | Monitor UUID |
| number | 10 | Number of incidents to return (1-100) |
list_channels
List notification channels (email, Slack, webhook, etc.).
No parameters required.
Example Prompts
"Show me all my cron monitors"
"Create a monitor for my daily backup that runs every 24 hours"
"Create a monitor for '*/5 * * * *' called 'Health check'"
"What's the status of my database cleanup monitor?"
"Show me the last 20 pings for monitor abc-123"
"Pause the nightly report monitor"
"Has my backup job had any incidents recently?"
"List my notification channels"
How It Works
Your AI agent receives a request about cron job monitoring
The agent calls WatchCron tools (list, create, check status, etc.)
The MCP server communicates with the WatchCron API
Results are returned to the AI agent in a readable format
Typical workflow
You: "Set up monitoring for my backup script that runs at 2am daily"
Agent: Creates a monitor with cron expression "0 2 * * *"
Returns the ping URL
You: Add to your crontab:
0 2 * * * /path/to/backup.sh && curl -fsS https://watchcron.com/ping/xxx > /dev/nullRequirements
Node.js 18+
A WatchCron API key (sign up)
Other Projects by WatchCron
ScreenshotRun — Screenshot API for developers and AI agents
SnapshotArchive — Automated website monitoring with visual diff detection
License
MIT
Available Tools
9 toolscreate_monitorA
Create a new cron job monitor. Returns the ping URL that your cron job should call. Supports simple interval (every N seconds) or cron expression schedules.
Inputs: name (required), schedule_type (required), tags, timezone, +4 more.
delete_monitorB
Permanently delete a cron job monitor. This cannot be undone.
Inputs: uuid (required).
get_incidentsA
Get status change history (incidents) for a monitor. Shows when the monitor went down, recovered, or changed status.
Inputs: uuid (required), limit.
get_monitorA
Get detailed information about a specific cron job monitor, including its status, schedule, ping URL, last ping time, and next expected ping.
Inputs: uuid (required).
get_pingsB
Get recent ping history for a monitor. Shows when pings were received, their type (success/start/fail), source IP, and duration.
Inputs: uuid (required), limit.
list_channelsA
List notification channels configured in your WatchCron project (email, Slack, webhook, etc.).
Inputs: no named parameters.
list_monitorsA
List all cron job monitors in your WatchCron project. Shows name, status, schedule, last ping time, and ping URL for each monitor.
Inputs: tag.
pause_monitorA
Pause or resume a cron job monitor. Paused monitors won't trigger alerts when pings are missed.
Inputs: uuid (required), paused.
update_monitorC
Update an existing cron job monitor's settings (name, schedule, grace period, tags).
Inputs: uuid (required), name, tags, timezone, +5 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
Each tool has a distinct resource+action target: monitor CRUD is split cleanly across list/get/create/update/delete, with pause_monitor covering the orthogonal state toggle. get_pings and get_incidents target clearly separate history types, and list_channels is the only channel tool, so there are no ambiguous boundaries.
All tools follow a consistent snake_case verb_noun pattern (list_monitors, get_monitor, create_monitor, delete_monitor, get_pings, get_incidents). The single deviation, pause_monitor, still fits the pattern even though it also resumes.
Nine tools is well-scoped for a cron monitoring service, with each tool earning its place across the lifecycle (create/list/get/update/delete) plus observability and notification surfaces. No redundant or filler tools.
Monitor lifecycle is fully covered (create, list, get, update, delete, pause/resume) with ping and incident history reads, so core workflows have no dead ends. The gap is channels: list_channels exists with no create/update/delete-channel counterpart, and there is no manual ping/test trigger.
Related MCP Connectors
Manage Cronitor monitors, issues, status pages, and metrics for jobs, uptime, and sites.
Cron, uptime, DNS, SSL and domain monitoring. Manage checks, dashboards and alerts; read incidents.
Manage scheduled requests, uptime monitors and heartbeats from your AI assistant.
Create, test, and manage uptime monitors for websites and APIs from your AI agent.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Uptime Agent monitoring system to check uptime status, manage incidents, create new monitors, and analyze downtime through natural conversation.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Healthchecks.io, allowing users to list, create, update, pause, resume, and delete checks, as well as view ping history and integrations.78 npm1MIT
- AlicenseAqualityCmaintenanceEnables users to manage OmniWatchGuard website monitors and alerts via natural language. Supports listing, creating, updating, pausing, resuming, and deleting monitors, plus reviewing recent notifications across channels.7547 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables assistants to monitor cron jobs, investigate failures via runs and incidents, and create or manage monitors through the Tickwatch API.MIT