Croncool

What croncool MCP server does

The croncool MCP server gives an AI agent access to operational information about scheduled automation in Croncool. Its documented scope covers four inspection areas: scheduled jobs, job runs, durable workflows, and webhook health. These capabilities help an agent examine what is scheduled, review run-related information, inspect workflow state, and check the health of webhooks.

The server also exposes a controlled execution action. An agent can run one confirmed job rather than receiving unrestricted job execution. That distinction matters when the agent is being used for operational support: inspection can inform a decision, while the run action requires confirmation before the job is started.

Tools and capabilities

The documented capabilities of the croncool MCP server include:

• Inspect scheduled jobs.
• Inspect runs.
• Inspect durable workflows.
• Inspect webhook health.
• Run one confirmed job.

These capabilities are oriented toward scheduled-task visibility and a narrowly defined operational action. The available material does not describe filtering options, returned fields, run history depth, workflow mutation, webhook management, or support for creating and editing jobs. Do not assume those functions are available from this listing.

How it works

An MCP-compatible agent uses the server to request information about Croncool scheduling resources and to invoke the documented job action. Inspection and execution are separate use cases: the inspection tools provide visibility into jobs, runs, workflows, and webhook health, while the execution capability is limited to running a single confirmed job.

The confirmation requirement is the clearest workflow constraint described for execution. A practical interaction can therefore involve checking the relevant scheduled job or recent run first, inspecting related workflow or webhook health information when needed, and then confirming the single job run. The source material does not specify the transport, authentication flow, response format, or confirmation protocol, so those details require the project’s developer documentation.

Limitations and notes

The croncool MCP server’s documented feature set is concise. The available listing does not provide installation instructions, configuration variables, client-specific setup, licensing information, or a detailed tool schema. It also does not state whether the server supports job creation, job updates, cancellation, retries, log retrieval, or webhook changes.

Use the server for the listed inspection and confirmed-run tasks, and verify the current Croncool developer documentation before planning an integration that depends on setup details or capabilities beyond those five functions.