Cron ⇒ webhook · MCP · streamable-http

cron-mcp

Schedule any prompt on any cron expression. When it fires, we POST to your callback URL. Your agent (Claude, Cursor, custom code) does the thinking — we just store schedules and fire webhooks. No LLM in our stack, no vendor lock-in.

View on GitHub ↗

Mental model

Your agent  →  schedule_job(cron, prompt, callback_url)
                            │
                            ▼
                   cron-mcp stores it
                            │
                    (cron matches at 8am)
                            │
                            ▼
     cron-mcp POSTs { jobId, name, prompt, metadata, firedAt }
     to your callback_url, signed with X-Cron-Signature
                            │
                            ▼
             Your callback runs the prompt through
             the LLM + tools and delivers the result.

Limits (per API key)

Jobs per user

20 max

Fire interval

5 min minimum

Cost

Free forever

Fair-use caps to keep the free tier free. Building an aggregator platform that needs more? Email shreyas.pavuluri@gmail.com.

Setup

1. Sign in above.
2. Copy your MCP API key from the dashboard.
3. Paste this into your agent's config:

{
  "mcpServers": {
    "cron": {
      "url": "https://cron.regiq.in/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_KEY>"
      }
    }
  }
}

Then have your agent call schedule_job with a cron expression, prompt text, and the URL to POST to when it fires.

MCP tools

• schedule_job(name, cron, prompt, callbackUrl, ...) — create a job.
• list_jobs() — return everything you own.
• get_job(id) — one job + last 20 fire attempts.
• update_job(id, ...) — partial update, or pause via isActive: false.
• delete_job(id) — permanent.

Webhook payload

POST <your callback_url>
Content-Type: application/json
X-Cron-Signature: sha256=<hex-hmac-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. Return any 2xx status to mark the fire as ok.