Cron Mcp

Name: Cron Mcp
Author: Shreyas-Profile

by Shreyas-Profilecommunityv0.1.0

Cron-as-a-service MCP server that lets an agent schedule prompts on cron expressions and sends each firing as a signed POST request to a user-provided callback URL. It also supports listing, fetching, updating, and deleting scheduled jobs.

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

GitHub Repository

Install & configure

Prerequisites

required
Create a Cron MCP account and API key
Sign in to the hosted Cron MCP service and generate an MCP API key from the dashboard.
https://cron.regiq.in/
required
Provide a webhook callback endpoint
You need a callback URL that Cron MCP can POST scheduled job payloads to when a cron job fires.
required
Configure webhook signature verification secret
Your callback should verify the X-Cron-Signature header using your shared signing secret. The README refers to this secret as CRON_WEBHOOK_SIGNING_SECRET.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `cron-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Create a Cron MCP account and API key** — Sign in to the hosted Cron MCP service and generate an MCP API key from the dashboard. (https://cron.regiq.in/)
- **Provide a webhook callback endpoint** — You need a callback URL that Cron MCP can POST scheduled job payloads to when a cron job fires.
- **Configure webhook signature verification secret** — Your callback should verify the X-Cron-Signature header using your shared signing secret. The README refers to this secret as CRON_WEBHOOK_SIGNING_SECRET.

Canonical MCP server config (HTTP transport):
- url: `https://cron.regiq.in/api/mcp`
- headers:
  - `Authorization`: `Bearer <your-api-key>`

Note: Hosted service uses HTTP MCP with Bearer authentication. The README also documents a self-hosted Docker Compose deployment, but the hosted URL is the simplest portable path. Self-hosting setup requires Docker/Compose, Google OAuth credentials, a public HTTPS base URL, NEXTAUTH_SECRET, and CRON_WEBHOOK_SIGNING_SECRET, but no canonical MCP client command/args/env shape is provided for self-hosted use beyond pointing clients at the deployed HTTP endpoint.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Hosted service uses HTTP MCP with Bearer authentication. The README also documents a self-hosted Docker Compose deployment, but the hosted URL is the simplest portable path. Self-hosting setup requires Docker/Compose, Google OAuth credentials, a public HTTPS base URL, NEXTAUTH_SECRET, and CRON_WEBHOOK_SIGNING_SECRET, but no canonical MCP client command/args/env shape is provided for self-hosted use beyond pointing clients at the deployed HTTP endpoint.

Tools (5)

schedule_job

Create a scheduled prompt with a cron expression, prompt, and callback URL.

list_jobs

Return all jobs owned by the calling API key.

get_job

Return a single job and its last 20 fire attempts.

update_job

Partially update a job, including pausing it by setting isActive to false.

delete_job

Permanently delete a job.

Environment variables

CRON_WEBHOOK_SIGNING_SECRETrequiredShared secret used to sign webhook payloads and verify the X-Cron-Signature header.

Remote Endpoints

https://cron.regiq.in/api/mcp

type: streamable-http

Details

Language: TypeScript
License: MIT
Released: Jul 16, 2026
Last commit: Jul 17, 2026
Registry name: io.github.Shreyas-Profile/cron-mcp

Related Servers

Context7

Up-to-date code docs for any prompt

60.8k

Openmetadata Mcp

Official OpenMetadata MCP: governed context and business semantics for AI assistants and agents.

14.9k

Tolgee

Your app's translations in Tolgee: search keys, create translations, trigger machine translation

4.1k