Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud
Cron MCP
Overview
Description from the maker (original English)
Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 0 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- You fill in yourself:
Authorization
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http cron https://cron.regiq.in/api/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cron": {
"url": "https://cron.regiq.in/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"cron": {
"type": "http",
"url": "https://cron.regiq.in/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
AuthorizationHTTP headerBearer — get yours at https://cron.regiq.in after Google sign-in.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ! Caution
Maker matches the repo
The publisher (Shreyas-Profile) is not the repo owner (globalion); someone else may have listed it
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Search & AI memoryi
- More stars than 0% of the other 5756 servers in this category
- Published to the registry more recently than 23% of the other 5756 servers in this category
- Basic checks equal to or better than 16% of the other 5756 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Cron MCP safe?
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud✓ exa.ai
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
cron-mcp
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](https://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" } } } }
- Have your agent call
schedule_jobwith 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/json X-Cron-Signature:
{ "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:/api/auth/callback/google - A public HTTPS domain (Cloudflare Tunnel or
ngrok http 3015locally)
No LLM key required. Your callback is where inference happens.
git clone https://github.com/globalion/cron-mcpcd cron-mcp cp .env.example .env
fill NEXTAUTH_SECRET, GOOGLE_*, PUBLIC_BASE_URL, CRON_WEBHOOK_SIGNING_SECRET
docker 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.
License
MIT. See LICENSE.