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., "@cronmcp add a job to check server health every hour"
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.
cronmcp is an open-source cron scheduler stdio MCP server built on top of cron, cron-parser, commander, and @modelcontextprotocol/sdk.
It lets MCP-compatible clients create and manage scheduled prompt jobs, and optionally subscribe to cron tick notifications through an MCP notification channel.
Exposes cron scheduling as an MCP server over stdio.
Uses the cron package for in-process job execution.
Validates schedules as 5-field local cron (M H DoM Mon DoW).
Persists jobs in JSONL under ~/.cronmcp/crontab.
Provides tools to list, add, update, and remove jobs.
Supports one-shot schedules through once: true.
Can emit scheduled tick events over an optional MCP notification channel.
Related MCP server: silentwatch-mcp
Node.js 24+
Use it without installing globally:
npx cronmcp mcpOr for local development:
npm install
npm run build
npm run dev -- mcpStart the MCP server:
npx cronmcp mcpIf your MCP host supports notifications and you want tick events, enable channels:
npx cronmcp mcp --channelsThe server uses stdio, so it is meant to be launched by an MCP client or wrapper rather than browsed directly in a terminal.
npx cronmcp mcpStarts the stdio MCP server with job persistence at ~/.cronmcp/crontab.
The server currently exposes these tools:
cron_list_jobs
cron_add_job
cron_update_job
cron_remove_job
schedule values use local-time 5-field cron: minute hour day-of-month month day-of-week.
When started with --channels, the server:
advertises the experimental MCP capability hooman/channel
advertises hooman/user with path meta.user
advertises hooman/session with path meta.session
advertises hooman/thread with path meta.thread
emits notifications/hooman/channel for scheduled cron tick events
Each notification includes:
content: a JSON-encoded event payload
meta.source: cron (channel contract)
meta.user: scheduler
meta.session: the cron job ID
meta.thread: omitted for cron tick events
The JSON-decoded content payload includes:
source
job
prompt
tickedAt
cronmcp stores local state under ~/.cronmcp/:
crontab for JSONL job records
Each record shape:
{
"id": "job_34a56f84-cf7e-4f8d-810c-1777d9f4a5f1",
"schedule": "*/5 * * * *",
"prompt": "Check queue depth",
"once": false,
"createdAt": 1777098600000
}Cron expressions must be valid 5-field local schedules.
Jobs must have a next run within the next year.
At most 50 jobs can be scheduled at once.
Recurring jobs auto-expire after 7 days (they fire one final time, then are removed).
Recurring jobs use deterministic jitter to avoid synchronized fire spikes.
once: true jobs are removed after the first successful tick.
Incoming notification channels depend on MCP host support.
MIT. See LICENSE.
This server cannot be deployed
Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL.
timesheet.io MCP server - manage timers, projects, tasks and reports
MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
Schedule and manage recurring or one-shot tasks