Command-line access to your cron jobs on app.cron.cool: projects, scheduled jobs, their schedules and HTTP targets, and each job's last execution status — plus running a job immediately or deleting it.
npm install -g croncool # global install
npx croncool --help # or run without installingRequires Node.js 18 or newer.
croncool login # opens the browser to authorize the CLI
croncool projects list # your projects with their ids
croncool jobs list --projectId PROJECT_IDFound 2 job(s):
1. warm-cache [rate(5 minutes)] (64a1f2c9e4b0a1b2c3d4e5f6)
2. nightly-report [cron(0 3 * * ? *)] (64a1f2c9e4b0a1b2c3d4e5f7)
croncool login starts a temporary localhost server, opens your browser to
app.cron.cool, and receives the session tokens on the redirect back. If the
browser does not open, the login URL is printed so you can visit it by hand.
Tokens are stored in ~/.croncool/ and refreshed automatically when they
expire; croncool logout clears them. A 401 error ending with
"Not logged in?" means there is no valid session — run croncool login and
retry.
croncool login # log in via browser; tokens land in ~/.croncool/
croncool logout # clear the stored sessioncroncool projects list # list projects with name and id
croncool projects get [projectIdOrName] # one project (or all) as a raw object dump
croncool projects read <projectIdOrName> # formatted view: organizationId, countryCode, timestampscroncool jobs list # 10 most recent jobs (-n/--limit, --projectId)
croncool jobs get <jobId> # one job as a raw object dump
croncool jobs get --projectId <id> -n 20 # no jobId: dump an array of jobs
croncool jobs read <jobId> # formatted view: schedule, url, method, enabled,
# last execution, timestamps
croncool jobs execute <jobId> # fire the job's configured request immediately
croncool jobs delete <jobId> # delete the job (no confirmation prompt)--projectId can be omitted when a croncool.json supplies it — see
Configuration below. get prints the object in Node's inspect format —
readable, but not strict JSON.
execute sends the HTTP request configured on the job right away; the
downstream target runs for real, so double-check the job id first with
croncool jobs read. delete removes the job immediately and cannot be
undone.
croncool skills list # names and descriptions of the bundled agent guides
croncool skills get croncool # print a bundled SKILL.md to stdoutA croncool.json in the working directory (or any directory below it)
supplies the default --projectId for jobs list and jobs get:
{ "projectId": "64a1f2c9e4b0a1b2c3d4e5f6" }Explicit CLI options take priority over the file.
CRONCOOL_API_URL overrides the API endpoint (default
https://api.cron.cool) — only needed against a non-production deployment.
Install the Croncool agent skills — croncool (this CLI) and
scheduler-operations (the MCP-based scheduled-operations workflow) — for
Claude Code, Cursor, Codex, and any other agent that supports the Skills
standard:
npx skills add croncool/skillsThe same guides ship inside the npm package, version-matched to the installed CLI:
croncool skills list # what is bundled
croncool skills get croncool # the CLI guide matching this versionOr paste this into your AGENTS.md / CLAUDE.md:
## Cron jobs
Use the `croncool` CLI for Croncool data: projects, scheduled jobs, their
schedules and last execution status. Run
`npx croncool skills get croncool` for the full guide, and
`croncool --help` for the command reference. Log in once with
`croncool login`.Prefer a connector? The Croncool MCP server at https://mcp.cron.cool/mcp
exposes the same data as tools for Claude, ChatGPT, and any MCP-capable host
— see cron.cool/developers.