analyze_cron_collisions — cron collision detector MCP Tool
analyze_cron_collisions
(analyze cron collisions) is one of 2 tools on the
cron collision detector
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_cron_collisions from your client
- Claude Code cron collision detector analyze_cron_collisions run in your project directory
- Claude Desktop cron collision detector analyze_cron_collisions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor cron collision detector analyze_cron_collisions ~/.cursor/mcp.json
- VS Code cron collision detector analyze_cron_collisions .vscode/mcp.json
- Zed cron collision detector analyze_cron_collisions ~/.config/zed/settings.json
- Windsurf cron collision detector analyze_cron_collisions ~/.codeium/windsurf/mcp_config.json
- Cline cron collision detector analyze_cron_collisions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI cron collision detector analyze_cron_collisions ~/.gemini/settings.json
- Grok cron collision detector analyze_cron_collisions .mcp.json (in your project root)
- ChatGPT cron collision detector analyze_cron_collisions Settings → Connectors → Advanced → Developer mode
- Claude.ai cron collision detector analyze_cron_collisions Settings → Connectors → Add custom connector
- LangChain cron collision detector analyze_cron_collisions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cron-collision-detector https://api.lazy-mac.com/cron-collision-detector/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.