croncool

Name: croncool
Author: cron

Inspect scheduled jobs, runs, durable workflows, and webhook health; run one confirmed job.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

What data it sees

Do you need an account

No: the server works without sign-in

Inspect scheduled jobs, runs, durable workflows, and webhook health; run one confirmed job.

How to connect

How to connect croncool to Claude

The server address to paste into Claude settings:

https://mcp.cron.cool/mcp

Open Claude (claude.ai or the desktop app).
Go to Settings → Connectors.
Click Add custom connector.
Paste the server address copied below into Remote MCP server URL and click Add.
In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect croncool to ChatGPT

The server address to paste into ChatGPT settings:

https://mcp.cron.cool/mcp

Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
Open Settings → Connectors and click Create.
Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect croncool to Cursor

The server address to paste into Cursor settings:

https://mcp.cron.cool/mcp

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (10)

Raw names from tools/list. Only developers need these.

list_projects	List a bounded set of Croncool projects the authenticated user can access. Returns only the project id needed for follow-up calls, display name, and creation time; workflow callback configuration and secrets are excluded.
list_jobs	List a bounded page of Croncool jobs in the authenticated organization, optionally filtered by exact project id. Returns safe scheduling metadata and target origins only; request payloads and credential-bearing URL paths, queries, fragments, or userinfo are excluded. Reuse nextCursor with the same filter to continue.
get_job	Fetch a single Croncool cron job by exact id. Returns safe scheduling metadata and only the target HTTP(S) origin; request payloads and credential-bearing URL paths, queries, fragments, or userinfo are never returned. Jobs owned by another organization are reported as not found.
run_job	Trigger one existing Croncool job by exact id immediately, outside its schedule. This is destructive under host review policy, open-world, and non-idempotent: every call can send the configured request again and cause downstream writes, messages, billing, or third-party effects. First call get_job, show the exact job and target origin, and obtain the user's explicit confirmation. Never retry automatically after a timeout or ambiguous error; inspect get_job_runs first.
get_job_runs	Fetch a bounded execution history for one exact Croncool job id, most recent first. Returns execution id, status, HTTP status, duration, and timestamp only; response bodies, errors, job request payloads, and credentials are excluded. Use this after run_job to verify the recorded outcome instead of retrying automatically.
list_workflows	List a bounded set of durable workflows for one exact Croncool project id with per-status run counts and most recent run time. Workflow inputs, outputs, error messages, callback configuration, and secrets are excluded.
list_workflow_runs	List a bounded page of durable workflow runs for one exact Croncool project id, optionally filtered by workflow name and status. Returns only run identity, status, timings, and machine error code; workflow inputs, outputs, and error messages are excluded. Reuse nextCursor with identical filters to continue.
get_workflow_run	Fetch one durable workflow run by exact project id and run id together with a bounded set of steps. Returns status/timing metadata and machine error codes only; workflow inputs, outputs, error messages, deployment details, and ownership fields are excluded. Cross-organization ids are reported as not found.
list_webhook_subscriptions	List a bounded set of webhook delivery-health records in the authenticated Croncool organization, optionally filtered by exact project id. Returns endpoint origins, event filters, active state, failure counts, and delivery times. Full endpoint paths/queries, signing secrets, payloads, and ownership fields are excluded. Endpoints are automatically disabled after 20 consecutive failures. Requires a logged-in user session, not the stdio API-key transport.
show_project_overview	Render a bounded overview for one known Croncool project id. Use after list_projects. Shows safe project metadata and up to 12 tenant-scoped jobs with target origins only; job request payloads, credential-bearing target paths/queries, organization fields, and workflow callback secrets are excluded.