Cron Tools

io.github.basitalisandhuPublished by GitHub account basitalisandhuv0.3.0Updated Oct 29, 2026

Parse, explain and validate 5-field cron expressions and list upcoming runs in a time zone.

The publisher's own server: Croncool Cron Jobs

Overview

AI-generated overview

Parses, explains, validates and schedules 5-field cron expressions, listing upcoming and past run times in a chosen time zone.

What you can do
  • Parse a cron expression into per-field values, wildcard flags, normalised form and macro expansion
  • Explain an expression as one plain English sentence
  • Validate an expression and report errors and warnings such as OR day semantics or impossible dates
  • List upcoming run times, or past runs before a given moment, in local time with offset and in UTC
When to use it
Useful when writing or reviewing crontab entries, GitHub Actions schedules or other Vixie-style schedulers and you want the schedule explained, checked, or previewed in a specific time zone, including DST edge cases.
Requirements
Runs as a local stdio process, typically via Docker with the pinned image; a Node.js checkout build is also possible. No accounts, API keys or environment variables are declared, and it needs no network access.
Before you install
Read-only: it parses and computes schedules but does not install or modify any crontab. Only 5-field Vixie cron is supported; seconds fields and L, W and # are rejected. Run-time results depend on the time zone and from arguments you supply.

Installation

In SourceWeft

  1. Open Cron Tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

cron-tools MCP server

Parses, explains, validates and schedules 5-field cron expressions in the Vixie cron dialect (Linux crontab, GitHub Actions, most schedulers), including lists, ranges, steps, month and weekday names, 0 or 7 for Sunday and the @hourly to @yearly macros. Time zone arithmetic uses Intl only; there are no dependencies beyond the MCP SDK and zod.

Part of dev-mcp-servers. Stdio transport only; the server never opens a port.

Tools

ToolInputWhat it returns
parse_cronexpressionPer field: raw text, wildcard flag and every accepted value; plus the normalised expression and macro expansion.
explain_cronexpressionOne English sentence, for example */15 9-17 * * 1-5 is "At every 15th minute past every hour from 9 through 17 on Monday through Friday."
validate_cronexpressionvalid, errors, and warnings: both day fields restricted (OR semantics), days that never occur in the chosen months, 7 for Sunday, ? spelling, macro expansion.
next_runsexpression, count? (1 to 100), timezone? (IANA), from? (ISO 8601)Upcoming run times in local time with offset and in UTC. Wall-clock times skipped by a forward DST transition are not run that day; a repeated hour runs twice. Stops after ten years.
previous_runsSame inputs as next_runsRun times strictly before from, newest first, in local time with offset and in UTC. Uses the same DST semantics and ten-year horizon.

Install

Claude Code:

bash
claude mcp add cron-tools -- docker run --rm -i ghcr.io/basitalisandhu/mcp-cron-tools:0.3.0

Add -s user to make it available in every project. Any client that reads .mcp.json (Claude Code, Claude Desktop, Cursor):

json
{  "mcpServers": {    "cron-tools": {      "command": "docker",      "args": ["run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-cron-tools:0.3.0"]    }  }}

Pin the version as shown so that an update cannot change what runs in your editor without you noticing. The package is not on npmjs.com yet, so npx does not work; see the repository README for GitHub Packages npm. From a checkout, use "command": "node", "args": ["<path>/packages/cron-tools/dist/index.js"] after npm install && npm run build at the repository root.

What it touches

  • Network: None.
  • Local files: None.
  • Telemetry: none.

Notes

  • Seconds fields (6-field Quartz) and L, W, # are rejected with an explanation.
  • When both day-of-month and day-of-week are restricted, a day matches if either does, as in Vixie cron.

Build and test

bash
npm install        # at the repository rootnpm run build -w @basitalisandhu/mcp-cron-toolsnpm test -w @basitalisandhu/mcp-cron-tools

Tests use node:test and the SDK's in-memory transport; they do not reach the network.

Licence

MIT. See LICENSE.

Source: packages/cron-tools/README.md at commit b211222

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

5
  1. v0.3.0LatestOct 29, 2026
  2. v0.2.2Oct 18, 2026
  3. v0.2.1Oct 13, 2026
  4. v0.2.0Oct 9, 2026
  5. v0.1.1Oct 5, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Cron integrations