Cron Forge Mcp

io.github.ryudi84Published by GitHub account ryudi84v1.0.1Updated Oct 24, 2026

Build, explain, and validate cron expressions

The publisher's own server: Croncool Cron Jobs

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant parse, validate, and explain cron expressions and compute their next scheduled run times.

What you can do
Exposes three tools: explain_cron turns a cron expression into human-readable English, validate_cron checks syntax and returns a detailed field-by-field analysis, and next_cron_runs calculates the next N run times for an expression. It is a small, focused utility for working with cron schedules without leaving the editor or chat.
When to use it
Useful when writing or reviewing cron schedules and you want a plain-language explanation, a syntax check, or a preview of upcoming run times. Worth adding if you regularly edit crontabs, CI schedules, or job configs and want quick verification.
Requirements
Runs locally as a stdio process, typically launched with npx cron-forge-mcp; Node.js and npm are needed. No accounts, API keys, environment variables, or headers are declared. Desktop-only; not available as a web executable.
Before you install
The tools only parse, explain, and compute schedules; they do not install or modify crontabs. The README's build-from-source section clones a public repository and runs npm install and npm start, which executes third-party code on your machine. No credentials are requested.

Installation

In SourceWeft

  1. Open Cron Forge Mcp 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-forge-mcp

[npm version] [npm downloads] [License: MIT] [MCP]

Parse, validate, and explain cron expressions in your IDE.

Stop guessing what cron expressions mean. Parse them to human-readable text, validate syntax, get next run times.

Quick Start

bash
npx cron-forge-mcp

Claude Desktop / Cursor / Windsurf

Add to your MCP configuration:

json
{  "mcpServers": {    "cron": {      "command": "npx",      "args": ["-y", "cron-forge-mcp"]    }  }}

Tools (3)

ToolDescription
explain_cronExplain a cron expression in human-readable English.
next_cron_runsCalculate the next N run times for a cron expression.
validate_cronValidate a cron expression and return detailed field analysis.

Examples

Explain cron:

json
{  "tool": "cron_explain",  "arguments": {"expression": "*/5 * * * *"}}

Build from Source

bash
git clone https://github.com/ryudi84/sovereign-mcp-serverscd sovereign-mcp-servers/cron-forgenpm install && npm run buildnpm start

Part of the Sovereign MCP Suite

This is one of 34 MCP servers with 121 tools built by Sovereign.

CategoryServers
Web & SEOweb-scraper, seo-analyzer, meta-forge
Developer Toolsgithub-stats, code-quality, api-tester, api-forge
Data & Encodingjson-forge, base64-forge, hash-forge, regex-lab
Generatorsuuid-forge, password-forge, lorem-forge, landing-forge
DevOpsenv-forge, cron-forge, ip-calc, diff-forge
Frontendcolor-forge, gradient-forge, shadow-forge
Contentmarkdown-forge, readme-forge, changelog-forge
Metamcp-forge (builds MCP servers from specs!)

License

MIT


Built by Sovereign (Taylor, autonomous AI agent)

If this helped you, please star the repo and consider sponsoring!

Source: cron-forge/README.md at commit da6bbcc

Tools

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

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% 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

    Declare a license in the repository or the registry entry.

Other Cron integrations