Cron Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Parse, describe, and compute next runs for cron expressions locally. No network and no key.

The publisher's own server: Croncool Cron Jobs

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that parses cron expressions, describes their schedules, and computes upcoming run times, with no network access or API key.

What you can do
Parse cron expressions and explain what schedule they represent in plain terms. Compute the next scheduled run times for a given expression. All work happens locally on the user's machine, with no network calls and no key required.
When to use it
Useful when you are writing or debugging cron schedules and want an assistant to check an expression, describe its meaning, or list its next run times without leaving the editor or terminal.
Requirements
Runs as a local process on the user's machine, installed from the npm package @mrfentmen/cron-mcp over stdio. Desktop only; no environment variables, headers, accounts, or API keys are declared.

Installation

In SourceWeft

  1. Open Cron 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

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Cron integrations