Cron Translator
v0.1.0Explain cron expressions in English, list next run times, and catch scheduling gotchas.
Endpoint health
online- Last checked
- 11/20/2026, 6:16:57 AM
- Latency
- 117 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.crontoenglish%2Fcron-translator
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.crontoenglish/cron-translator": {
"url": "https://crontoenglish.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
3 shown · authentication unknown
Build a cron expression from English
build_cron
Convert an English schedule description into a standard five-field cron expression, then explain and validate the result. Use this when a user describes a schedule in words and needs the expression. This is a RULE-BASED converter, not a language model: it handles a fixed grammar and returns an error listing the supported phrasings when a phrase falls outside it. That refusal is deliberate — a plausible-looking wrong schedule is worse than no answer. If a phrase is rejected, rephrase it into one of the supported shapes and call again. Returns the expression, which rule matched, any words the rules did not use (check these — leftover words may mean the phrase was misread), the English description of the result, warnings, and the next run times.
Schema valid · SHA-256 277918e52649…
View input schema
{ "type": "object", "properties": { "phrase": { "type": "string", "description": "An English schedule description, for example \"every weekday at 9am\" or \"on the 1st of every month at midnight\". Times accept 24-hour (\"14:30\"), 12-hour (\"2:30pm\"), \"midnight\", and \"noon\"." }, "timezone": { "default": "UTC", "description": "IANA timezone name, for example \"UTC\", \"America/New_York\", or \"Europe/Berlin\". Cron expressions carry no timezone of their own, so this decides when the schedule actually fires. Defaults to UTC.", "type": "string" } }, "required": [ "phrase" ], "$schema": "https://json-schema.org/draft/2020-12/schema" }Explain a cron expression
explain_cron
Translate a cron expression into plain English, list its upcoming run times in a specific timezone, and report the gotchas that make schedules misfire. Use this whenever a cron expression needs to be read, verified, or explained — and prefer it over reasoning about the expression directly. Cron has several counter-intuitive rules that are easy to get wrong: day-of-month and day-of-week are combined with OR (not AND) when both are set, steps like */7 do not divide their field evenly, dates like February 30 never fire at all, and daylight-saving transitions skip or repeat runs. This tool checks all of them. Returns the normalised expression, a one-sentence description, a per-field breakdown, a list of warnings with severity and a fix for each, the next run times as both UTC ISO 8601 instants and local wall-clock strings, and an approximate runs-per-day figure.
Connections
streamable-http
https://crontoenglish.com/api/mcp