mcp-crontab-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-crontab-server Explain cron expression */15 9-17 * * 1-5"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Crontab Server
An MCP server for exploring, explaining, and managing crontab entries. Works with Claude Desktop, Claude Code, and any MCP client.
Standout features: Explain cron expressions in plain English and calculate upcoming execution times — no more guessing what */15 9-17 * * 1-5 means.
Quick Start
Claude Desktop
Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"crontab": {
"command": "uvx",
"args": ["mcp-crontab-server"]
}
}
}Claude Code
claude mcp add crontab -- uvx mcp-crontab-serverInstall from source
git clone https://github.com/jalloway/mcp-crontab-server.git
cd mcp-crontab-server
pip install -e .
mcp-crontab-serverRelated MCP server: mcp-crontab
Tools
Tool | Description |
| List all crontab entries for the current user |
| Search entries by keyword (case-insensitive) |
| Recent cron execution logs (journalctl / syslog) |
| Explain a cron expression in plain English |
| Calculate the next N execution times |
| Check if an expression is syntactically valid |
| Add a new entry to the user's crontab |
| Remove entries matching a pattern |
Example Conversations
"What does this cron expression mean?"
explain_cron_expression("*/15 9-17 * * 1-5")Every 15 minutes, from 9:00 AM through 5:59 PM, Monday through Friday
"When will this job run next?"
next_runs("0 2 * * 0", count=3)Next 3 runs for '0 2 * * 0':
2026-03-01 02:00:00 Sunday
2026-03-08 02:00:00 Sunday
2026-03-15 02:00:00 Sunday
"Is this valid?"
validate_cron_expression("60 * * * *")Invalid: Value 60 out of range (0-59) in minute field
Development
pip install -e .
# Run with MCP inspector
fastmcp dev src/mcp_crontab_server/server.py
# Run directly (stdio transport, default)
mcp-crontab-server
# Run with SSE transport
mcp-crontab-server --transport sseRequirements
Python 3.10+
Linux/macOS (uses
crontabcommand)fastmcp>=2.0.0,croniter>=1.0.0
Available Tools
8 toolsadd_cron_entryA
Add a new entry to the current user's crontab.
Inputs: command (required), schedule (required). Returns: result
explain_cron_expressionA
Explain a cron expression in plain English. Supports 5-field cron and special strings like @daily.
Inputs: expression (required). Returns: result
get_cron_logsA
Get recent cron execution logs from the system.
Inputs: lines. Returns: result
list_crontabA
List all crontab entries for the current user with line numbers.
Inputs: no named parameters. Returns: result
next_runsA
Calculate the next N execution times for a cron expression.
Inputs: expression (required), count. Returns: result
remove_cron_entryA
Remove crontab entries matching a pattern. Shows what will be removed.
Inputs: pattern (required). Returns: result
search_crontabA
Search crontab entries containing a keyword (case-insensitive).
Inputs: keyword (required). Returns: result
validate_cron_expressionA
Check if a cron expression is syntactically valid. Returns specific errors for invalid fields.
Inputs: expression (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: list/search target entries, add/remove modify entries, get_cron_logs retrieves logs, and the three expression tools (explain, validate, next_runs) each return different outputs. There is no overlap that would confuse an agent.
Most tools follow a verb_noun pattern (list_crontab, search_crontab, add_cron_entry, etc.) with consistent snake_case. The exception is 'next_runs', which is a noun phrase rather than verb-first, and 'get_cron_logs' uses 'get' while others use different verbs, but the overall pattern is still readable.
8 tools is well-scoped for a crontab manager: entry operations (list/search/add/remove), log retrieval, and cron expression utilities (explain/validate/next_runs). Each tool serves a distinct need, and the count is appropriate.
The surface covers the core workflows: viewing (list/search), modifying (add/remove), checking execution (logs), and handling expressions (explain/validate/next_runs). An update/edit tool is missing, which would be a minor gap, but re-adding after removal is a workaround.
Maintenance
Related MCP Connectors
Validate and explain cron expressions; list next/previous run times in any time zone, DST-aware.
Explain cron expressions in English, list next run times, and catch scheduling gotchas.
Deterministic time tools for AI agents: timezone conversion, business-day math, cron interpretation.
Manage cron jobs, machines and run history in your norc account from any AI chat.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI agents to parse, validate, explain, and preview cron expressions, surfacing common silent bugs before deployment.458 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides tools to parse and describe cron expressions in plain English, and compute future run times.77 npmMIT
- AlicenseNot gradedqualityCmaintenanceParse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.1MIT
- AlicenseNot gradedqualityDmaintenanceParses cron expressions, returns next fire times, and provides an English description.MIT