create_job
Create a new cron job with a schedule and shell command
LABSCO SUMMARY
Keeping exit codes and output per execution is what separates this from crontab, where a failing job is silent until someone notices the effect.
The reason cron jobs rot is that nothing records what happened — a job that started failing three weeks ago looks exactly like one that is working. Storing the output, duration and exit code per run, with a success rate rolled up, turns that into something readable. run_now is the other tool that earns its place: the normal way to test a cron job is to wait, and waiting is how a broken schedule reaches production. Be clear about what this is: it executes shell commands on the host, so it is exactly as powerful as the account it runs under.
What it is
A cron job manager with ten tools covering the job lifecycle and, importantly, its execution history: schedule, modify, pause, trigger manually, and read logs and success rates.
What you get
- Jobs created with a schedule and a shell command, updated in place rather than recreated, and deleted along with their run history.
- pause_resume disables a job without deleting it, which is what you want before a maintenance window.
- run_now executes immediately bypassing the schedule — the tool that makes a new job testable before you wait for its first trigger.
- get_status returns last run, next run, success rate and average duration, so a job's health is a number rather than an impression.
- get_logs returns a job's execution output with duration and exit code, and list_executions covers recent runs across every job.
Requirements
A host to schedule on. The jobs are shell commands, so they run with whatever permissions the server has.
Setup effort
One command — npx -y @supernova123/cron-scheduler-mcp-server
USE CASES
01
Scheduling something and knowing it works
Create the job, run it immediately to see it succeed, and only then leave it to the schedule.
02
Finding out why the output stopped appearing
Read the job's execution logs with exit codes and durations, rather than inferring failure from a missing side effect.
03
Standing a job down for maintenance
Pause it and resume afterwards, instead of deleting and recreating it and losing the history.
04
Changing a schedule or a command
Update the job in place, keeping its identity and its run history intact.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
delete_job
Remove a scheduled job and its run history
get_job
Get detailed information about a specific cron job including configuration, stats, and recent runs
get_logs
Get execution logs for a job with output, duration, and exit code
get_status
Get detailed job status: last run, next run, success rate, average duration, and error history
list_executions
List recent executions across all jobs with status, duration, and job name
list_jobs
List all scheduled cron jobs with their status, next run time, and last run result
pause_resume
Pause or resume a scheduled job without deleting it
run_now
Execute a job immediately, bypassing its schedule
update_job
Modify an existing job's schedule, command, or settings without recreating it
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"cron-scheduler-mcp-server": {
"command": "npx",
"args": [
"-y",
"@supernova123/cron-scheduler-mcp-server"
]
}
}
}npx
TERMINAL
npx -y @supernova123/cron-scheduler-mcp-server
