Cron Mcp

io.github.Shreyas-Profile由 GitHub 帳號 Shreyas-Profile 發布v0.1.0更新於 Oct 24, 2026

Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL.

發布方自己的服務：Croncool Cron Jobs

已驗證Streamable HTTP可網頁執行效率與工作流開發者工具

服務詳細資訊

識別碼: io.github.Shreyas-Profile/cron-mcp
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 Shreyas-Profile。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Shreyas-Profile%2Fcron-mcp.svg)](https://sourceweft.com/mcp/io.github.Shreyas-Profile%2Fcron-mcp?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

排程即服務的 MCP，讓助理安排週期性提示詞，並在觸發時把任務 POST 到你指定的回呼網址。

可以做什麼: 建立、列出、檢視、更新與刪除排程提示詞任務，每個任務包含名稱、cron 表示式、提示詞與回呼網址
將任務設為非啟用以暫停，或永久刪除任務
檢視單一任務詳情及其最近 20 次觸發紀錄
任務觸發時以帶簽章的 webhook 形式 POST 到你的回呼，由你的代理執行提示詞
適用情境: 適合需要讓助理依固定週期安排重複工作的情境，例如每日簡報、每小時輪詢、每週摘要，而真正的模型呼叫發生在你自己的回呼端點，而非此服務上。
執行需求: 使用託管的遠端端點，需在儀表板以 Google 或 GitHub 登入後產生 MCP API 金鑰，並以 Authorization Bearer 標頭送出。自架需要 Docker 與 Compose、Google OAuth 用戶端、公開的 HTTPS 網域，以及 NEXTAUTH_SECRET、GOOGLE_* 變數、PUBLIC_BASE_URL 與 CRON_WEBHOOK_SIGNING_SECRET 等設定。回呼網址必須可公開存取。

安裝前請注意

此服務會在其伺服器上保存你的排程、提示詞與回呼網址。助理可以建立、更新並永久刪除任務。回呼帶有 X-Cron-Signature 簽章，請以 CRON_WEBHOOK_SIGNING_SECRET 驗證後再信任內容。回呼失敗只會被記錄，排程仍會繼續推進，若不監控則不易察覺。

安裝

在 SourceWeft 中

開啟儀表板中的 Cron Mcp，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.Shreyas-Profile%2Fcron-mcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "cron": {
      "type": "http",
      "url": "https://cron.regiq.in/api/mcp"
    }
  }
}

README

cron-mcp

Built by Shreyas · Shipped by Globalion

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):

json

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

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

Have your agent call schedule_job with a cron expression, a prompt, and the URL you want us to POST to when it fires.

Tools

Tool	Purpose
`schedule_job(name, cron, prompt, callbackUrl, ...)`	Create a scheduled prompt.
`list_jobs()`	Return every job owned by the calling key.
`get_job(id)`	One job + the last 20 fire attempts.
`update_job(id, ...)`	Partial update. Set `isActive: false` to pause.
`delete_job(id)`	Permanent delete.

Webhook payload

When a job fires, we POST:

POST <your callbackUrl>Content-Type: application/jsonX-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"}

POST <your callbackUrl>Content-Type: application/jsonX-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/google
A public HTTPS domain (Cloudflare Tunnel or ngrok http 3015 locally)

No LLM key required. Your callback is where inference happens.

bash

git clone https://github.com/globalion/cron-mcpcd cron-mcpcp .env.example .env# fill NEXTAUTH_SECRET, GOOGLE_*, PUBLIC_BASE_URL, CRON_WEBHOOK_SIGNING_SECRETdocker compose up -d# open http://localhost:3015

git clone https://github.com/globalion/cron-mcpcd cron-mcpcp .env.example .env# fill NEXTAUTH_SECRET, GOOGLE_*, PUBLIC_BASE_URL, CRON_WEBHOOK_SIGNING_SECRETdocker compose up -d# open http://localhost:3015

Architecture

  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.

  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.