cron-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_cronA | Parse a cron expression and return a human-readable description of when it fires. Supports 5-field standard cron (min hour dom month dow) plus extensions: L (last day/weekday), W (nearest weekday), # (nth weekday), and named months/days (JAN..DEC, SUN..SAT). Use this to explain any cron schedule in plain English. |
| validate_cronA | Deeply validate a cron expression for correctness and common mistakes. Catches: impossible schedules (e.g. day 31 in Feb), OR-semantics gotchas (dom AND dow both restricted = either matches, not both), midnight scheduling spikes, uneven step values (*/7), leap-year edge cases, weekday-only warnings, and more. Returns warnings, observations, optimization suggestions, and an estimated yearly run count. Use this BEFORE deploying a cron job to catch silent failures. |
| next_runsA | Compute the next N scheduled run times for a cron expression. Returns ISO-8601 timestamps with relative offsets (+5m, +1h, +2d). Use this to preview when a job will actually fire before committing it. |
| cron_presetsA | Return a library of common cron expression presets (every 5 min, hourly, daily at midnight, weekdays 9am, monthly, quarterly, yearly, etc.) with their plain-English labels. Use this when a user asks for a "common" or "standard" schedule and you want to offer proven starting points. |
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 4 tools
Each tool serves a distinct purpose: parse (human-readable description), validate (error detection), next_runs (future schedule preview), and cron_presets (common schedules). No overlaps.
All tool names follow a consistent verb_noun pattern in snake_case: parse_cron, validate_cron, next_runs, cron_presets.
With 4 tools, the server covers the essential operations for a cron utility: parsing, validation, preview, and preset library. Not too few or too many.
The tool set covers core cron tasks (parse, validate, preview, presets). Minor gaps include no tool to generate a cron expression from natural language or handle timezones explicitly, but these are not critical.