Crondex MCP Server

A public directory of pre-made, agent-editable cron jobs — usable as a CLI or as an MCP server. The crondex mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Works with Claude, Codex, Hermes, OpenClaw, or any plain LLM with shell access.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• deploy — -list-installed — show every crondex-managed line in your
• category — jobs
• agency — 35
• agriculture — 41
• automotive — 35
• banking — 35
• childcare — 43
• cleaning-services — 35
• construction — 41
• content — 35
• coworking — 35
• creator — 35

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Crondex.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the crondex mcp server does with a few real requests.

When to reach for it

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Crondex's toolset — deploy, category, agency and 11 more — is a fair guide to whether it matches your workflow. It is maintained by wonsukchoi; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Crondex's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.