Croncool Cron Jobs MCP Server

by cron Your server? Claim it

answering

Croncool Cron Jobs is answering right now. Last checked 14 min ago. It exposes 11 tools.

Check your cron jobs, recent runs, workflows and webhooks, and run a job now when you confirm.

Uptime history 88 days of history

88 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

603 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 33

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 September 2026. No other catalogue keeps this.

17 Oct 11 tool descriptions were rewritten get_job, get_job_runs, get_workflow_run and 8 more

5 Oct a tool description was rewritten open_croncool

2 Oct a tool appeared open_croncool

28 Sep 10 tool descriptions were rewritten get_job, get_job_runs, get_workflow_run and 7 more

28 Sep 9 tools changed the parameters they ask for get_job_runs, get_workflow_run, list_jobs and 6 more

27 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check Croncool Cron Jobs every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add croncool --transport http https://mcp.cron.cool/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.cron.cool/mcp

~/.codex/config.toml

[mcp_servers.croncool]
url = "https://mcp.cron.cool/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

job

get_job

Use this when the user wants to read the scheduling configuration and latest execution metadata of one CronCool job selected by its exact identifier. 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 the user wants to read execution history for one CronCool job to inspect success, failure, HTTP status and duration. 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.

run_job

Use this when the user wants to immediately execute the configured request for one CronCool job. 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.

workflow

get_workflow_run

Use this when the user wants to read one CronCool workflow execution and a bounded page of its step statuses for troubleshooting. 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_workflow_runs

Use this when the user wants to list executions of a durable workflow in CronCool, with optional workflow-name and status filters. 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.

jobs

list_jobs

Use this when the user wants to list scheduled jobs in CronCool to inspect schedules, enabled state and the latest execution status. 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.

open

open_croncool

Use this when the user wants to open the CronCool project-selection sidebar when the user requests an interactive project and job browser. 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.

projects

list_projects

Use this when the user wants to list projects accessible to the connected CronCool account, including identifiers needed to select a project. 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.

show

show_project_overview

Use this when the user wants to render a read-only overview of one CronCool project and a bounded preview of its scheduled jobs. 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.

webhook

list_webhook_subscriptions

Use this when the user wants to read CronCool webhook subscription configuration and recorded delivery failures. 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.

workflows

list_workflows

Use this when the user wants to list durable workflow definitions and run-count summaries for one CronCool project. 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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.cron.cool/mcp	streamable-http	answering	533 ms	14 min ago

Alternatives to Croncool Cron Jobs

same job, measured the same way

Cwl MCP

by mrfentmen

Common Workflow Language MCP: read, check, lint, scaffold and run code.

local only

Studio

by kaitoi

Build and run visual creative-production workflows from your AI agent.

answering

Agenttrio

by cloudcorprecords

Bounded planner-coder-reviewer workflows: status, verified run, and configured checks.

311 installs/wk local only

Whenever

by whenever

Write, validate, deploy and run TypeScript workflow automations on Whenever from your coding agent.

answering

WebArm24

by webarm24

AI automation platform (n8n/Zapier alternative): build, schedule and run workflows from your agent.

89 tools answering

Wiro AI

by wiro

Run Wiro AI models, build and run workflows, and talk to Studio and your Wiro agents.

1 213 installs/wk answering

Migrate to n8n

by kotiniiqq

Convert Make and Zapier automations into n8n workflows, with a report of what to check.

73 installs/wk local only

Recipe360

by pulso360

Your AI runs your data workflows the same way every time, with a record of every run.

local only

Croncool Cron Jobs — questions

Answers built from our own checks of this server.

What can Croncool Cron Jobs do?

It exposes 11 tools, read directly from the server on our last check. Among them: get_job, get_job_runs, get_workflow_run, list_jobs, list_projects, list_webhook_subscriptions and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Croncool Cron Jobs mostly used for?

Its tools cluster around job and workflow. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Croncool Cron Jobs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 603 ms. The bar chart above shows every period we have measured.

How do I connect Croncool Cron Jobs?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Croncool Cron Jobs need an API key?

No. Croncool Cron Jobs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Croncool Cron Jobs?

It answers our handshake in 603 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.