cronjob-org-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRONJOB_API_KEY | Yes | Your cron-job.org API key, obtainable from the console under Settings > API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_jobsA | List all cron jobs in the cron-job.org account. |
| get_jobA | Get full details (including auth, notifications, headers, body) for one cron job by ID. |
| create_jobA | Create a new cron job on cron-job.org. Only 'url' is mandatory; omitted schedule fields default to 'every unit' ([-1]), so an empty schedule runs every minute of every day. |
| update_jobB | Update an existing cron job. Only include the fields you want to change. |
| delete_jobB | Permanently delete a cron job by ID. |
| get_job_historyA | List recent executions of a cron job, plus predicted upcoming execution timestamps. |
| get_history_itemA | Get full details (including response headers/body if saved) for one execution history entry. |
| list_foldersA | List all folders used to organize cron jobs. |
| get_folderB | Get details for one folder by ID. |
| create_folderA | Create a new folder to organize cron jobs into. Title must be unique, max 128 characters. |
| update_folderC | Rename an existing folder. |
| delete_folderA | Delete a folder. Jobs inside it are not deleted; they become unfoldered. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct resource and action: jobs, folders, and history are cleanly separated. Even get_job_history and get_history_item are clearly list-versus-detail operations.
All tools follow a consistent verb_noun snake_case pattern using list/get/create/update/delete. The naming clearly conveys both the operation and the resource being operated on.
Twelve tools is well-scoped for managing cron-job.org: full CRUD for jobs and folders, plus history retrieval. Each tool covers a necessary operation without redundancy.
The tool surface provides complete job lifecycle coverage (create, read, update, delete, list), folder organization coverage, and execution history access. No obvious dead ends or missing critical operations.