Cron Collision Detector
Detect overlapping cron schedules in production configs so background jobs do not stampede databases or APIs.
Overview
io.github.lazymac2x/cron-collision-detector is an MCP server for the Operate phase that helps agents detect overlapping cron schedules via a remote Workers API.
What is this MCP server?
- MCP server on Cloudflare Workers with streamable-http remote
- Focused on cron-collision-detector workflows for scheduled task overlap
- GitHub source cron-collision-detector-api for server implementation reference
- Agent-callable checks without installing a separate collision CLI locally
- Version 1.0.0 hosted endpoint on api.lazy-mac.com
- Server version 1.0.0 per registry JSON
- Single streamable-http remote endpoint
- Cloudflare Workers; GitHub cron-collision-detector-api
What problem does it solve?
Scheduled jobs pile up at the same minute and you only notice when queues spike or locks contend.
Who is it for?
Builders operating several cron-driven workers or batch jobs who want agent-assisted schedule overlap checks.
Skip if: Products with no scheduled jobs or teams that already use enterprise job orchestration with built-in conflict policies.
What do I get? / Deliverables
You connect the MCP remote so agents can flag cron collisions while you edit infra or scheduler configs.
- Agent tools to surface cron schedule collisions
- Safer schedule changes before deploy
- Documented v1.0.0 remote MCP registration
Recommended MCP Servers
Journey fit
How it compares
MCP infra helper for cron overlap, not a cron monitor dashboard or PaaS scheduler UI.
Common Questions / FAQ
Who is cron-collision-detector for?
Solo operators and small teams managing multiple cron triggers who use MCP agents to review schedule safety.
When should I use cron-collision-detector?
Use it when adding new crons, migrating schedules, or debugging thundering herds in Operate and infra work.
How do I add cron-collision-detector to my agent?
Add https://api.lazy-mac.com/cron-collision-detector/mcp as a streamable-http MCP server in your client settings.