Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL.
Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL. That is what the cron mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: CRON_WEBHOOK_SIGNING_SECRET, PUBLIC_BASE_URL, NEXTAUTH_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by Shreyas-Profile; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Cron's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"cron": {
"url": "https://cron.regiq.in/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY_HERE"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CRON_WEBHOOK_SIGNING_SECRET | Credential the server authenticates with. | Yes |
| PUBLIC_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| NEXTAUTH_SECRET | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.