cron-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
cron-mcp
Cron-as-a-service MCP. Schedule any prompt on any cron expression; when it fires we POST the job to your callback URL. No LLM in our stack.
Your agent (Claude Desktop, Cursor, a custom script) does the thinking. We just:
store the schedule + prompt + your callback URL
match minutes against the cron expression
POST the job body to your callback, signed with
X-Cron-Signature
That's it. Perfect for daily briefings, hourly polls, weekly digests, or anything else that repeats on a fixed schedule and needs to run through an LLM.
Hosted at cron.regiq.in or self-host with the Docker Compose below.
Use it (hosted)
Visit https://cron.regiq.in, sign in with Google or GitHub.
Generate an MCP API key on the dashboard, copy it.
Add to Claude Desktop's
claude_desktop_config.json(or Cursor / any MCP client):{ "mcpServers": { "cron": { "url": "https://cron.regiq.in/api/mcp", "headers": { "Authorization": "Bearer YOUR_KEY_HERE" } } } }Have your agent call
schedule_jobwith a cron expression, a prompt, and the URL you want us to POST to when it fires.
Related MCP server: cron-mcp
Tools
Tool | Purpose |
| Create a scheduled prompt. |
| Return every job owned by the calling key. |
| One job + the last 20 fire attempts. |
| Partial update. Set |
| Permanent delete. |
Webhook payload
When a job fires, we POST:
POST <your callbackUrl>
Content-Type: application/json
X-Cron-Signature: <hex-hmac-sha256-of-body>
{
"jobId": "clx...",
"name": "daily AI news briefing",
"prompt": "summarise the top 5 AI news items from the last 24h",
"metadata": { ... },
"firedAt": "2026-07-16T08:00:00.412Z"
}Verify the signature by re-hashing the raw body with your shared signing secret (env CRON_WEBHOOK_SIGNING_SECRET) and comparing to the X-Cron-Signature header. Return any 2xx to mark the fire as ok — anything else is logged as a failure and the schedule still advances (so a failing callback won't stop future runs).
Self-host
You'll need:
Docker + Compose
A Google OAuth client — Cloud Console. Scopes:
openid,email,profile. Redirect:<PUBLIC_BASE_URL>/api/auth/callback/googleA public HTTPS domain (Cloudflare Tunnel or
ngrok http 3015locally)
No LLM key required. Your callback is where inference happens.
git clone https://github.com/globalion/cron-mcp
cd cron-mcp
cp .env.example .env
# fill NEXTAUTH_SECRET, GOOGLE_*, PUBLIC_BASE_URL, CRON_WEBHOOK_SIGNING_SECRET
docker compose up -d
# open http://localhost:3015Architecture
Your agent Your callback
│ ▲
│ schedule_job(cron, prompt, │
│ callback_url) │
▼ │
┌──────────────────────────────────────────────────┐
│ cron-mcp (Hetzner) │
│ - /api/mcp Bearer-auth JSON-RPC │
│ · schedule_job, list, get, update, delete │
│ - Postgres: User, ApiKey, Job, JobRun │
│ - Scheduler loop (60s tick) — matches cron, │
│ POSTs signed webhook to callback_url, │
│ logs a JobRun row per fire. │
└──────────────────────────────────────────────────┘
│
│ POST (signed)
▼
Your callback runs the
prompt through the LLM +
tools and delivers the result.License
MIT. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL.
Reliable scheduling for one-off and recurring webhooks, built for apps and agents.
Schedule tasks for later from your AI agent: reminders, delayed webhooks, recurring jobs.
Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables scheduling and triggering reminders delivered via Slack or Telegram through natural language, using an external cron service to ensure delivery even when the server is offline.417 npm15MIT
- AlicenseNot gradedqualityDmaintenanceSchedule any prompt on any cron expression; when it fires, we POST the job to your callback URL. No LLM in the stack.MIT
- FlicenseNot gradedqualityCmaintenanceEnables ChatGPT to schedule future proactive messages and receive queued events into conversations through MCP Apps, without calling the OpenAI API.-
- AlicenseNot gradedqualityCmaintenanceEnables users to schedule and manage prompts for Codex CLI sessions, supporting one-time, interval, and cron triggers for both existing and newly created sessions.8 npm1MIT