Skip to main content
Glama
Sign In
cronjob-org-mcp

cronjob-org-mcp

by darshk07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cronjob-org-mcp

An MCP server for cron-job.org's REST API. Lets any MCP-compatible client (Claude, Claude Code, etc.) create, inspect, update, and delete cron jobs and folders, and read execution history, using natural language.

Tools

Tool

Description

list_jobs

List all cron jobs

get_job

Get full details for one job

create_job

Create a new job

update_job

Update an existing job

delete_job

Delete a job

get_job_history

List recent executions + predicted next runs

get_history_item

Get full details of one execution

list_folders

List folders

get_folder

Get one folder

create_folder

Create a folder

update_folder

Rename a folder

delete_folder

Delete a folder

Related MCP server: UptimeRobot MCP Server

Setup

  1. Get an API key from your cron-job.org console under Settings > API.

  2. Add the server to your MCP client's config, for example in Claude Desktop's claude_desktop_config.json or Claude Code's MCP settings:

{
  "mcpServers": {
    "cronjob-org": {
      "command": "npx",
      "args": ["-y", "cronjob-org-mcp"],
      "env": {
        "CRONJOB_API_KEY": "your-api-key-here"
      }
    }
  }
}

  1. Restart your client. The tools above should now be available.

Notes

  • The free cron-job.org tier is limited to 100 API requests/day (5,000/day for sustaining members). Bulk operations may hit this limit.

  • create_job and update_job accept a schedule object (hours, minutes, mdays, months, wdays, each [-1] for "every"), plus timezone, auth (HTTP basic auth), notification (failure/recovery/cert-expiry alerts), and headers/body for the request payload. Only url is required to create a job.

  • requestMethod is numeric: 0=GET, 1=POST, 2=OPTIONS, 3=HEAD, 4=PUT, 5=DELETE, 6=TRACE, 7=CONNECT, 8=PATCH.

Development

npm install
npm run build
cp .env.example .env   # then edit .env and paste in your API key
npm run inspector      # launch the MCP Inspector against the built server

The .env file is picked up automatically — no need to export environment variables in your shell. It's git-ignored, so your key never gets committed.

License

MIT

Available Tools

12 tools
create_folderCreate a folderA

Create a new folder to organize cron jobs into. Title must be unique, max 128 characters.

Inputs: title (required).

create_jobCreate a cron 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.

Inputs: url (required), auth, body, title, +9 more.

delete_folderDelete a folderA

Delete a folder. Jobs inside it are not deleted; they become unfoldered.

Inputs: folderId (required).

delete_jobDelete a cron jobB

Permanently delete a cron job by ID.

Inputs: jobId (required).

get_folderGet folder detailsB

Get details for one folder by ID.

Inputs: folderId (required).

get_history_itemGet a single execution's detailsA

Get full details (including response headers/body if saved) for one execution history entry.

Inputs: jobId (required), identifier (required).

get_jobGet cron job detailsA

Get full details (including auth, notifications, headers, body) for one cron job by ID.

Inputs: jobId (required).

get_job_historyGet cron job execution historyA

List recent executions of a cron job, plus predicted upcoming execution timestamps.

Inputs: jobId (required).

list_foldersList foldersA

List all folders used to organize cron jobs.

Inputs: no named parameters.

list_jobsList cron jobsA

List all cron jobs in the cron-job.org account.

Inputs: no named parameters.

update_folderRename a folderC

Rename an existing folder.

Inputs: title (required), folderId (required).

update_jobUpdate a cron jobB

Update an existing cron job. Only include the fields you want to change.

Inputs: url (required), jobId (required), auth, body, +10 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 12 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Resources

    Related MCP Connectors

    Related MCP Servers