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.