About Cronicorn
Cronicorn schedules HTTP endpoint jobs and adapts their polling frequency based on response data and plain-English descriptions. It is for teams managing endpoint monitoring and recovery; conventional cron or interval scheduling remains available without AI.
Key features
- 01Adaptive polling schedules
- 02Plain-English job descriptions
- 03Minimum and maximum intervals
- 04Coordination across endpoints
- 05Automatic retries and recovery
- 06Cron and interval fallback
Use cases
- 01Adjust polling as endpoint activity changes
- 02Coordinate schedules for related endpoints
- 03Retry jobs after endpoint failures
- 04Manage jobs through a web UI or API
MCP support
Cronicorn provides an MCP server for managing jobs from Claude, Cursor, or another MCP client.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @cronicorn/mcp-serverCRONICORN_API_URLAPI base URL for CronicornCRONICORN_WEB_URLWeb UI URL for Cronicorn (used for OAuth device flow)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README
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
Activity surge → AI tightens to 30s + triggers recovery actions → stabilizes → back to baseline
Features
How It Works
Getting Started
|
Docs · MCP Server · API · Self-Host · Support
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.