Cron Scheduler MCP Server
About
7 tools for AI agent cron job scheduling with SQLite persistence, retry logic, and structured observability. MIT license.
Details
- Author
- friendlygeorge
- Categories
- Developer Tools, Project Management, Automation, Other
Jump to
Setup
Install Cron Scheduler MCP Server in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/friendlygeorge/cron-scheduler-mcp-server
Follow the installation instructions in the repository README, then restart your MCP client.
MCP server for cron job scheduling with SQLite persistence, retry logic, and structured observability. Let AI agents create, manage, and monitor scheduled tasks through a clean tool interface.
Most cron libraries are designed for applications to embed. This server exposes cron scheduling as an MCP tool — agents can schedule jobs, monitor execution, retry failures, and query logs without touching the filesystem or crontab directly.
Companion server:System Monitoring MCPfor host health metrics. Together they give agents full infrastructure observability and control.
mcp-cron is AGPL — fine for personal use, problematic for enterprise agents and commercial deployments. This server uses MIT + SQLite persistence + retry logic for production workloads.
- 10 tools:list_jobs,create_job,update_job,delete_job,get_job,run_now,get_status,get_logs,list_executions,pause_resume
- SQLite persistence— jobs survive server restarts
- Retry logic— configurable retry count and delay with attempt tracking
- Structured logs— stdout/stderr capture, duration, exit codes per execution
- Observability— success rate, average duration, error history per job
- Webhook triggers— fire HTTP callbacks on job completion
- MIT license— enterprise-friendly, no copyleft restrictions
npx @supernova123/cron-scheduler-mcp-server
{ "mcpServers": { "cron-scheduler": { "command": "npx", "args": ["-y", "@supernova123/cron-scheduler-mcp-server"] } } }
Add to your MCP settings (.cursor/mcp.jsonor equivalent):
{ "mcpServers": { "cron-scheduler": { "command": "npx", "args": ["-y", "@supernova123/cron-scheduler-mcp-server"] } } }
List all scheduled jobs with status, next run time, and last run result.
Returns:Array of jobs with id, name, schedule, command, enabled status, next run time, last run result, and aggregate stats (success rate, total runs, avg duration).
Create a new cron job with a schedule and shell command.
Remove a scheduled job and its entire run history.
Execute a job immediately, bypassing its schedule. Useful for testing or manual triggers.
Returns:Run result with status, exit code, stdout/stderr (truncated to 2000 chars), and duration.
Get detailed job status including last run, next run, success rate, average duration, and recent error history.
Returns:Full job config, next scheduled run, whether currently running, aggregate stats, and last 10 runs with status/exit code/duration.
Get execution logs for a job with full stdout, stderr, duration, and exit code.
Pause or resume a job without deleting it. Paused jobs retain their schedule but won't execute until resumed.
- Cron expressions:Standard 5-field format
- /5 — every 5 minutes
- 0 9 1-5— weekdays at 9am
- 30 2 * 0— Sundays at 2:30am
- 30s— every 30 seconds
- 5m— every 5 minutes
- 1h— every hour
- Infrastructure automation:Schedule health checks, log rotation, cleanup scripts
- Data pipelines:Periodic data pulls, report generation, cache invalidation
- Agent workflows:Let AI agents schedule their own recurring tasks (monitoring, backups, notifications)
- DevOps:Scheduled deployments, canary checks, post-deploy verification
- Testing:Recurring integration tests, smoke checks, performance benchmarks
All job definitions and execution history are stored in a SQLite database. The database file persists across server restarts — jobs survive crashes and restarts without re-creation.
Real data from building and running this server:
- MCP Server Testing— testing strategies for MCP servers
- What 6,000 npm Downloads Taught Me— distribution and growth data
- The MCP Server Naming Playbook— how naming affects discoverability
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
A command-line interface to prompt users for their next plan or confirmation.
Durable MCP control plane for long-running Codex Desktop tasks.
A development management tool for project planning, task management, and development workflows.
Multi-agent coordination over MCP: atomic gap-free claims, file leases, a shared ledger, presence, handoffs, and a task graph. Remote Streamable HTTP; self-host (AGPL) or hosted.
Exposes Makefile targets as callable tools for AI assistants.
A server for managing sequential development tasks with configurable rules using external .mdc files.
Project management inside every AI coding tool — plans what's next, tracks every decision, stops drift.
Facilitates software development planning through an interactive and structured approach.
A tool for structured software development planning, helping to break down projects into tasks and track progress.
The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
