CronCool MCP server

Which servers in the official MCP registry are CronCool's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to CronCool

Whose server it is

Registry namecool.cron/croncoolverified in the MCP registry

The registry name sits under cron.cool. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools11
Server calls itselfcroncool-mcp
Server version0.1.1
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 459 ms.

Tools it offers11 tools · read 2026-10-13

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_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…
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…
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…
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…
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…
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…
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…
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…
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…
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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "croncool": {
      "type": "http",
      "url": "https://mcp.cron.cool/mcp"
    }
  }
}

OpenAPI spec

6 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.