Cronjob API via MCP: manage cronjobs with Claude, ChatGPT or Cursor
The interface to Cronjob.de is not a REST API but MCP. Connect your AI assistant to your account once, then just ask in plain language – „Which cronjobs failed yesterday?“, „Create one that runs on Sundays at 4am.“ or „Monitor my website and show it on my status page.“ Your assistant can do everything your account can: cronjobs, heartbeats, server monitoring, SSL certificates, notifications and status pages. No token, no config file.
https://www.cronjob.de/bridge
This is the address you enter in your assistant.
Connected in three steps
- Enter the address. In Claude under „Connectors“, in ChatGPT and Cursor at the corresponding place for MCP servers.
- Confirm in the browser. Cronjob.de opens, you sign in as usual and allow access. We show you which account the connection applies to.
- Done. Your assistant now knows your cronjobs. You can disconnect at any time under „AI access“.
What the assistant can do
| Tool | What for | Kind |
|---|---|---|
list_jobs |
List cronjobs | read only |
get_job |
View a cronjob | read only |
list_job_history |
Read the call log | read only |
get_job_timeline |
History of recent weeks | read only |
list_failures |
List failed calls | read only |
list_folders |
List folders | read only |
list_monitors |
List server monitors | read only |
get_monitor |
View a server monitor | read only |
list_ssl_certificates |
View SSL certificates | read only |
list_contacts |
View notifications | read only |
list_status_pages |
List status pages | read only |
create_job |
Create a cronjob | changes things |
create_heartbeat |
Create a heartbeat | changes things |
update_job |
Change a cronjob | changes things |
set_job_active |
Switch on or off | changes things |
move_job |
Move to a folder | changes things |
delete_job |
Delete a cronjob | changes things |
create_folder |
Create a folder | changes things |
create_monitor |
Create a server monitor | changes things |
update_monitor |
Change a server monitor | changes things |
set_monitor_active |
Switch a monitor on or off | changes things |
delete_monitor |
Delete a server monitor | changes things |
add_contact |
Add an alert contact | changes things |
set_alert_recipients |
Choose who gets alerts | changes things |
create_status_page |
Create a status page | changes things |
update_status_page |
Change a status page | changes things |
delete_status_page |
Delete a status page | changes things |
run_job_now |
Run a cronjob now | changes things |
Heartbeats and end signals via AI
Your assistant also sets up monitoring – for jobs on your own server as well as for cronjobs that Cronjob.de calls.
“Set up a heartbeat for my nightly backup, it runs at 3am.”
Your assistant creates the heartbeat and gives you the line for your crontab. If the backup does not check in on time, we alert you.
“Check whether my cronjob ‘Export’ runs to the end.”
Your assistant switches on the end signal and gives you the line for the end of your script. If that report does not arrive after a call, we alert you.
Security
- OAuth 2.1 with PKCE. No password in the assistant. You grant access in the browser, in your own session.
- Access tokens last one hour, refresh tokens 30 days and rotate on every use. If one is used twice, the whole chain is revoked.
- Only the hash is stored. Reading the database would not let anyone sign in.
- Every change is logged – with time, tool and the person who triggered it. At most 60 changing calls per hour.
- Disconnect at any time under „AI access“ in your account. The assistant then has to ask for access again.
- Servers exclusively in the EU. The contracting party is a German company; for personal data there is a data processing agreement under Art. 28 GDPR.
Is there a REST API?
No – and that is a decision, not a gap. For this purpose MCP does more: you manage no keys, there is no endpoint documentation to reimplement and no version that breaks under your feet. The assistant gets tools, not URLs. And you give up nothing: everything you do in your account also works via MCP – cronjobs, heartbeats, server monitoring, SSL, notifications and status pages, reading as well as changing.
- Sign-in without key management. OAuth 2.1 with PKCE, confirmed once in the browser. No token ageing in a configuration file.
- From your own scripts it works with any MCP client – they exist for Python, TypeScript and other languages.
- For servers without a browser there is a fixed token that does not expire. You find it in your account under „AI access“.
If you still need a classic interface, drop us a line saying what for. We will build it when enough people give the same reason.
It also works without your own assistant
You do not need a subscription with an AI provider. Your account contains an assistant that creates cronjobs from instructions – you paste the text, it fills in address, method and schedule. It is included in the free plan.