OpenApps

Croncool Scheduled Jobs & Workflows MCP server — tools & history

Croncool Scheduled Jobs & Workflows MCP server: observed open status, tool schemas, linked apps and version history.

Croncool Scheduled Jobs & Workflows

Endpoint: https://mcp.cron.cool/mcp

Observed status: open. Checked: 2026-10-12T05:10:45+00:00.

Linked apps

  • Croncool Scheduled Jobs & Workflows

    Inspect scheduled jobs, run history, durable workflows, and webhook health in Croncool. Run a job with explicit confirmation through its OAuth-protected MCP server.

Observed tools

  • get_job — Use this when someone asks about one cron job's schedule or target, or whether it is enabled and last succeeded. Returns the job's name, cron expression, type, target origin, HTTP method, content type, enabled state and last run status and time, or not-found. Not for running the job.
  • get_job_runs — Use this when someone asks whether a cron job ran, failed or was slow, including a run just triggered. Returns recent runs newest first with success or failure, HTTP status, duration and time (no response bodies), 20 by default and 100 at most. Not for starting a run.
  • get_workflow_run — Use this when someone asks why a durable workflow run failed or where it is stuck. Returns the run's status, timings and error code plus its steps with status, attempt, timings and error code, 50 steps by default and 200 at most. Not for listing runs.
  • list_jobs — Use this when someone asks what cron jobs or scheduled tasks they have, or which ones last failed. Returns each job's id, name, schedule, target origin, method, enabled state and last run status and time, 20 per page by default, with a cursor for more. Not for a job's full run history.
  • list_projects — Use this when someone asks which Croncool projects they have, or a project's id is needed. Returns each project's id, name and creation time, 50 by default and 100 at most, with a flag when more exist. Not for listing jobs.
  • list_webhook_subscriptions — Use this when someone asks whether their Croncool webhooks are delivering, failing or were disabled. Returns each subscription's endpoint origin, events, active state, consecutive failures, auto-disabled flag and last delivery time, 20 by default. Works only with a signed-in user session, not an API key. Not for changing or re-enabling a webhook.
  • list_workflow_runs — Use this when someone asks about recent or failed runs of a durable workflow in a Croncool project. Returns each run's id, workflow name, status, timings and error code, newest first by default, 20 per page with a cursor, filterable by workflow and status. Not for one run's steps.
  • list_workflows — Use this when someone asks which durable workflows a Croncool project runs, or how many runs are running, pending, completed, failed or cancelled. Returns each workflow's name, run counts by status and last run time for one project, 50 by default and 100 at most. Not for individual runs.
  • open_croncool — Use this when someone wants to open Croncool and browse their projects and scheduled jobs, with schedules, target origins and latest run status, in an interactive sidebar. Returns up to 100 projects to start from (no request payloads, workflow bodies, secrets or full target URLs). Not for running jobs or changing their configuration.
  • run_job — Use this when someone asks to run or trigger a cron job now. Returns only that Croncool invoked it, not the target's response. Each call immediately sends the job's configured request again, which can write, message or bill downstream, and a repeated call sends it once more. Not for checking a run's result.
  • show_project_overview — Use this when someone wants a quick overview or dashboard of one Croncool project. Returns an overview card with the project's name and creation time, whether workflow hosting is set up, and up to 12 jobs with schedule, target origin and last run status. Not for a job's run history.

Data as of 2026-10-12T05:10:45+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections