Cronicorn

io.github.weskerllcPublished by GitHub account weskerllcv1.25.0Updated Nov 3, 2026

Manage adaptive cron jobs and HTTP endpoint scheduling via AI assistants.

Overview

AI-generated overview

Cronicorn lets an assistant manage adaptive cron jobs and HTTP endpoint schedules, where AI adjusts polling frequency from response data.

What you can do
  • Add and manage HTTP endpoint jobs with a baseline cron or interval schedule
  • Describe in plain English what matters in responses, such as thresholds and coordination logic
  • Let the AI adapt polling frequency, coordinate sibling endpoints and trigger recovery actions
  • Rely on safety constraints such as min/max intervals and TTL-based hints that expire
  • Fall back to traditional cron and interval scheduling when AI adaptation is not wanted
When to use it
Useful when you want an assistant to set up and tune scheduled HTTP polling jobs, for example monitoring an API or endpoint whose ideal check frequency changes with its responses, instead of hand-editing cron configs.
Requirements
Runs as a local stdio process from the npm package @cronicorn/mcp-server, so Node.js is needed. Requires a Cronicorn account and the CRONICORN_API_URL environment variable; CRONICORN_WEB_URL is used for the OAuth device flow. Network access to the Cronicorn service is required. Desktop only.
Before you install
The server manages live scheduled jobs that call HTTP endpoints, so changes affect real recurring traffic and any actions those jobs trigger. It uses OAuth device flow sign-in against the configured web URL and sends job and response data to the Cronicorn service. Review min/max interval and TTL constraints before letting AI adjust schedules.

Installation

In SourceWeft

  1. Open Cronicorn in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Cronicorn] Cronicorn

HTTP jobs that understand their own responses

Add endpoints, describe what matters in plain English, and the AI reads response bodies to adapt —
adjusting frequency, coordinating siblings, and recovering from failures automatically

[Start Now (Free)]

[Cronicorn AI Adaptation]
Activity surge → AI tightens to 30s + triggers recovery actions → stabilizes → back to baseline

Features

  • Adaptive scheduling — AI adjusts polling frequency based on real response data
  • Plain English descriptions — no config files, no SDK required
  • Safety constraints — min/max intervals and TTL-based hints that auto-expire
  • Multi-endpoint coordination — endpoints are aware of siblings and adapt together
  • Automatic error recovery — backoff, retry, and recovery actions out of the box
  • Works without AI — traditional cron and interval scheduling as a fallback

How It Works

  1. Add an HTTP endpoint and set a baseline schedule (cron or interval)
  2. Describe what matters in plain English — thresholds, coordination logic, response structure
  3. AI monitors responses and adapts frequency, triggers actions, and recovers from failures automatically

Getting Started

PathLink
Web UI — create and manage jobs visuallycronicorn.com
MCP Server — manage jobs from Claude, Cursor, or any MCP clientMCP Server docs
API — integrate programmatically with the REST APIAPI Playground

Docs · MCP Server · API · Self-Host · Support

[License: FSL-1.1-MIT] [TypeScript] [Docs] [Image] [Context7 Verified]

Source: README.md at commit e9bd7d9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.25.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.