Croncool

The same projects, jobs and execution status are available from your terminal through the croncool CLI. Install it globally with npm, or run it ad hoc with npx.

Each key carries a list of scopes, so an integration that only needs to watch your jobs never gets the ability to change them. New keys start read-only; widen them explicitly in the dashboard. A request whose key is missing the scope an endpoint requires is refused with 403.

- jobs:readList your cron jobs and read a single job.
- jobs:writeCreate, update and delete jobs, and run one on demand.
- executions:readRead a job's execution history.
- workflows:readRead hosted workflow runs, steps, events and hooks.
- workflows:writeCreate workflow events, enqueue and dispatch work, cancel and replay runs.

The workflows:read and workflows:write scopes gate the endpoints the hosted workflow runtime calls on your behalf. The reference at /api/ covers the job and webhook subscription endpoints you call yourself; the workflow endpoints are not part of it.

Croncool’s remote MCP connector lets an assistant inspect the projects, jobs, executions, durable workflows and webhook delivery health already available to your signed-in organization. Add the same production URL in any host that supports remote MCP over HTTP:

Choose the host’s option to add a custom connector or MCP server, paste that URL, then complete Croncool’s OAuth sign-in and consent screen. Never paste an API key into a conversation. OAuth keeps every call inside the organization and scopes approved for that signed-in account.

- list_projectsFind accessible projects and their exact ids.
- list_jobsPage through safe job schedules and target origins within the authenticated organization.
- get_jobInspect one job’s schedule, method, target origin and latest status.
- get_job_runsReview bounded execution status, HTTP code, duration and time metadata.
- list_workflowsSummarize hosted workflow run counts for an exact project.
- list_workflow_runsPage through safe workflow status and timing metadata.
- get_workflow_runInspect one workflow run and a bounded step trace without payloads.
- list_webhook_subscriptionsAudit endpoint origins, event filters and delivery health without secrets.
- show_project_overviewRender a bounded project and job overview in compatible MCP hosts.
- run_jobRun one existing job now after explicit confirmation; every call can cause real downstream effects.

Connector results use field-by-field allowlists. Job request inputs, target URL userinfo, paths, queries and fragments, execution response bodies and errors, workflow inputs and outputs, webhook endpoint paths and queries, signing secrets, credentials, tokens and organization ownership fields are never model-visible. Target and webhook destinations are reduced to their HTTP or HTTPS origin.

run_job is the only state-changing connector tool. It invokes the request already configured on one exact job. That downstream service can write data, send messages, charge for work or trigger another third party. Croncool does not add an idempotency key or application timeout, so the outcome can be unknown after a transport timeout and repeating the call can duplicate effects. The assistant must first show the exact job and target origin, ask for explicit confirmation, invoke it once, and use get_job_runs to check the recorded outcome instead of retrying automatically.

- “List my Croncool projects and show the first project overview.”
- “Show failed runs of the nightly-sync workflow in this project, then inspect the newest failure.”
- “Audit my webhook subscriptions and flag any disabled after repeated delivery failures.”

# Install the Croncool skills into your coding agent npx skills add croncool/skills

One command installs the skills into Claude Code, Cursor, Codex, Gemini CLI and any other agent that follows the Skills standard. The CLI also bundles the same guides, version-matched to the commands it ships:croncool skills get <name>prints one on demand.

Add a webhook subscription to your project and Cron POSTs the events you picked to your server as they happen.

- job.createdA job was created.
- job.updatedA job was edited, paused or resumed.
- job.deletedA job was deleted.
- job.executedA job ran; the payload is the execution, with its status, http status, duration and truncated response body.

POST https://your-server.com/cron-webhook { "event": "job.executed", "timestamp": 1719000000, "data": { "...": "..." } }

Every delivery carries an X-Croncool-Signature header of the form t=timestamp,v1=signature, where the signature is an HMAC-SHA256 of timestamp.body keyed by the subscription secret shown to you once when the subscription was created. Recompute it over the raw body and compare before trusting the payload.