Your AI assistant writes the backup script in a minute. Then you still have to schedule it somewhere, and you have to notice when it stops running.
With MCP (Model Context Protocol), the assistant can do that part too. It creates the cron job, sets up monitoring, and later tells you which runs failed and why. The schedule runs on the cron service, so the chat doesn't have to stay open.
I'll use Cronjob.de for the examples, because that's the service I run. Other hosted schedulers offer MCP servers as well, and the steps are similar.
What MCP changes
MCP lets an assistant call tools of an outside service. A cron service exposes tools such as create_job, create_heartbeat or list_failures. You describe what you want, the assistant picks the tool and fills in the details. Most clients ask you before a call that changes something.
The assistant doesn't need to know the exact syntax of the service, and you don't need to switch to a dashboard for small changes.
Connecting the assistant
The MCP address is https://www.cronjob.de/bridge.
Claude (web and desktop): add a custom connector under Settings → Connectors and paste the address.
Claude Code:
claude mcp add --transport http cronjob https://www.cronjob.de/bridge
Then run /mcp inside Claude Code to sign in.
ChatGPT: add a custom connector with the same address, where your plan offers custom connectors.
Cursor and other MCP clients: add it as a remote server, for example in mcp.json:
{
"mcpServers": {
"cronjob": { "url": "https://www.cronjob.de/bridge" }
}
}
On first use a browser window opens. You sign in to your account and allow access (OAuth 2.1 with PKCE). No password or API key ends up in the assistant's configuration.
What you can ask
"Call https://example.com/cron.php every 15 minutes."
The assistant creates the job with that schedule and shows you what it saved.
"My backup runs at 3 am on my own server. Tell me if it doesn't."
This is a different case: the job runs elsewhere, so the service should watch for a signal instead of calling a URL. The assistant creates a heartbeat and gives you the line for your crontab:
0 3 * * * /path/to/backup.sh; curl -fsS -m 10 --retry 3 https://runcheck.de/<your-id>/$? > /dev/null
The /$? at the end sends the exit code of the script. You get an alert when the backup fails, and also when it doesn't report at all.
"Check whether my export job runs to the end."
A 200 from the trigger only means the request was accepted. With an end signal, the script reports when its last step is done, and the assistant gives you the line to add at the end of the script.
"Which jobs failed yesterday, and why?"
The assistant reads the failures with their status codes and error messages and sums them up. For a quick morning check, that's often faster than opening the dashboard.
"Monitor my website and show it on my status page."
Uptime checks and status pages work the same way.
Things worth checking
Time zones. Cronjob.de stores times in German time (Europe/Berlin). The assistant converts "9 am in New York" for you, but ask it to read the result back in your own time zone. Daylight saving time starts and ends on different dates in the US and in Europe, so a converted time can be off by an hour for a few weeks a year.
Deleting. The delete tool is marked as destructive and needs the exact name of the job, so a vague "clean up my jobs" can't wipe the account by accident. Still, read what the assistant wants to delete before you confirm. The history of a deleted job is gone too.
Limits and logs. Access tokens last one hour, and refresh tokens rotate on every use. If a refresh token is used twice, the whole chain is revoked. There are at most 60 changing calls per hour, and every change is logged with time and tool. You can disconnect the assistant at any time in your account.
Test the alert once. Break the URL on purpose, wait for the alert, then fix it. An alert you've never seen arrive is an assumption.
Without an AI subscription
You don't need an assistant with MCP to skip the cron syntax. The account has its own assistant: paste the instructions from your host or plugin documentation, and it fills in address, method and schedule. That one is in the free plan as well.
Who can use it
The MCP connection is part of the Unlimited plan and of the 14-day trial every new account starts with. Setup details and the full list of tools are on Manage cron jobs with AI.
I run Cronjob.de, so keep that in mind when reading the setup part.
Top comments (0)