MCP Connector

Manage Cron Tasks with LLM Applications

Cronlytic MCP Server manages cron jobs - creation, control, logs, and health checks - through Claude Desktop and other MCP clients.

Works with cronlytic

Maintainer of this project? Claim this page to edit the listing.


90
Spark score
out of 100
Updated Jun 2025
Version prod_0.1.0
Models
universal

Add to Favorites

Why it matters

Integrate LLM applications with your cron tasks for streamlined management. This MCP server allows for convenient creation, control, and monitoring of cron jobs through intelligent prompts.

Outcomes

What it gets done

01

Create, read, update, and delete cron tasks via LLM prompts.

02

Pause, resume, and monitor the execution of cron tasks.

03

Access execution logs and performance metrics for your cron jobs.

04

Perform health checks to ensure connectivity and authentication with the Cronlytic API.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-cronlytic | bash

Capabilities

Tools your agent gets

health_check

Tests connection and authentication with Cronlytic API, including API connectivity and authentication verification.

Overview

Cronlytic MCP Server

Integrates Claude Desktop and other MCP clients with the Cronlytic API for cron job management - health checks, CRUD, pause/resume, and log retrieval - with 9 tools claimed complete per the project's own status summary. Use when an assistant needs to manage or troubleshoot Cronlytic cron jobs conversationally; the source's roadmap section still uses in-progress phase language for most tools despite the project banner claiming full completion, so verify current tool behavior against a running server if precision matters.

What it does

Cronlytic MCP Server integrates with the Cronlytic API to let LLM applications like Claude Desktop manage cron jobs conversationally. The project's completion banner states all 6 development phases are finished, with 88/88 tests passing, 9 comprehensive tools covering the full job lifecycle, and 18 interactive prompts for guided assistance. The one tool documented with a full worked example is health_check, which takes no parameters and tests API connectivity, authentication validity, response times, and basic functionality, returning a status report with connection details, current job count, and a performance rating.

The remaining tool set, named in the source's phase-based roadmap section, covers basic CRUD (create_job, list_jobs, get_job, update_job, delete_job) and advanced job management (pause_job, resume_job, get_job_logs) - together with health_check this totals the 9 tools the completion summary claims. Note that this roadmap section still uses phase-in-progress language ("Phase 2: Basic CRUD Operations (Next)") even though the project banner elsewhere states all phases are complete, so treat the individual tool names as the documented tool set while verifying current behavior directly against a running server if precise per-tool parameters matter.

Beyond tools, the completion summary also references dynamic job resources, a cron template library, and interactive prompts for guided job creation and troubleshooting as part of the finished feature set.

When to use - and when NOT to

Use this when an AI assistant needs to create, monitor, pause, resume, or inspect the logs of scheduled cron jobs managed through Cronlytic, or simply verify that the Cronlytic API connection and credentials are working. Error handling is comprehensive by design: authentication errors get clear credential guidance, connection errors get network diagnostics, validation errors get field-by-field detail, API errors surface proper codes and user-friendly messages, and rate limiting triggers automatic retry with exponential backoff.

Capabilities

The server can be tested interactively with the MCP Inspector (mcp-inspector python -m cronlytic_mcp_server.server) and supports structured logging at multiple levels, including a --debug flag for verbose output. Development tooling includes black/ruff for formatting and linting and mypy for type checking.

How to install

Setup can use a bundled setup script or manual steps:

git clone https://github.com/Cronlytic/cronlytic-mcp-server.git
cd cronlytic-mcp-server
./setup_dev_env.sh
source venv/bin/activate

Credentials (CRONLYTIC_API_KEY, CRONLYTIC_USER_ID, obtained from the Cronlytic dashboard's API Keys section) can be supplied via environment variables, a JSON config file (checked at ./cronlytic_config.json, ~/.cronlytic/config.json, or /etc/cronlytic/config.json), or command-line arguments. For Claude Desktop, the server is registered in claude_desktop_config.json running python -m cronlytic_mcp_server.server with the API key and user ID passed through the env block.

Who it's for

Developers and teams using Cronlytic for cron job monitoring who want to create, control, and troubleshoot scheduled jobs conversationally through Claude Desktop or another MCP client.

Source README

Cronlytic MCP Server

๐ŸŽ‰ PROJECT COMPLETED - PRODUCTION READY ๐ŸŽ‰

A comprehensive Model Context Protocol (MCP) server that integrates with the Cronlytic API to provide seamless cron job management through LLM applications like Claude Desktop.

Final Status: โœ… All 6 phases complete | 88/88 tests passing | Production documentation ready

Overview

The Cronlytic MCP Server enables AI agents and LLM applications to:

  • ๐Ÿ” Health Check: Test connectivity and authentication with the Cronlytic API โœ…
  • ๐Ÿ“Š Job Management: Create, read, update, and delete cron jobs โœ…
  • โฏ๏ธ Job Control: Pause, resume, and monitor job execution โœ…
  • ๐Ÿ“ Logs & Monitoring: Access execution logs and performance metrics โœ…
  • ๐Ÿค– Smart Prompts: 18 comprehensive prompts for guided assistance โœ…
  • ๐Ÿ“š Resources: Dynamic job resources and cron templates โœ…
  • โšก Performance: Built-in monitoring and optimization โœ…

๐Ÿ† Project Status: ALL PHASES COMPLETED โœ…

๐ŸŽฏ Final Achievement Summary:

  • โœ… Phase 1: Core infrastructure and authentication
  • โœ… Phase 2: Basic CRUD operations (13 tests)
  • โœ… Phase 3: Advanced job management (22 tests)
  • โœ… Phase 4: Resources implementation (14 tests)
  • โœ… Phase 5: Prompts & UX (39 tests)
  • โœ… Phase 6: Testing & documentation (performance monitoring)

๐Ÿ“Š Key Metrics:

  • 88/88 Tests Passing (100% success rate)
  • 18 Interactive Prompts (225% of original scope)
  • 9 Comprehensive Tools (Full job lifecycle)
  • Complete Documentation Suite (8 detailed guides)
  • Production Ready (Multi-platform deployment support)

Installation

Prerequisites

  • Python 3.8 or higher
  • Cronlytic account with API access

Install from Source

Quick Setup (Recommended)
# Clone the repository
git clone https://github.com/Cronlytic/cronlytic-mcp-server.git
cd cronlytic-mcp-server

# Run the setup script (creates venv and installs everything)
./setup_dev_env.sh

# Activate the virtual environment
source venv/bin/activate
Manual Setup
# Clone the repository
git clone https://github.com/Cronlytic/cronlytic-mcp-server.git
cd cronlytic-mcp-server

# Create virtual environment
python3 -m venv venv
source venv/bin/activate

# Upgrade pip
pip install --upgrade pip

# Install dependencies
pip install -r requirements.txt

# Install development dependencies (optional)
pip install -r requirements-dev.txt

# Install in development mode
pip install -e .

Configuration

The server needs your Cronlytic API credentials to function. You can provide these in several ways:

Method 1: Environment Variables (Recommended)

export CRONLYTIC_API_KEY="your_api_key_here"
export CRONLYTIC_USER_ID="your_user_id_here"

Method 2: Configuration File

Create a configuration file at one of these locations:

  • ./cronlytic_config.json (current directory)
  • ~/.cronlytic/config.json (user home directory)
  • /etc/cronlytic/config.json (system-wide)
{
  "api_key": "your_cronlytic_api_key_here",
  "user_id": "your_cronlytic_user_id_here",
  "base_url": "https://api.cronlytic.com/prog",
  "timeout": 30,
  "max_retries": 3,
  "retry_delay": 1.0
}

Method 3: Command Line Arguments

python -m cronlytic_mcp_server.server --api-key "your_key" --user-id "your_id"

Getting API Keys

  1. Log into your Cronlytic dashboard
  2. Navigate to "API Keys" section
  3. Click "Generate New API Key"
  4. Copy your API key and User ID

Usage

Running the Server

# Basic usage (reads from environment variables or config file)
python -m cronlytic_mcp_server.server

# With command line arguments
python -m cronlytic_mcp_server.server --api-key "your_key" --user-id "your_id"

# With debug logging
python -m cronlytic_mcp_server.server --debug

# With custom config file
python -m cronlytic_mcp_server.server --config /path/to/config.json

Available Tools (Phase 1)

Health Check

Test connectivity and authentication with the Cronlytic API:

# The health_check tool requires no parameters
# It will test:
# - API connectivity
# - Authentication validity
# - Response times
# - Basic functionality

Example Output:

# Cronlytic API Health Check

**Status:** โœ… Cronlytic API connection is healthy and working correctly
**Timestamp:** 2025-01-27T10:30:00Z
**Response Time:** 150 ms

## Connection Details
- **Base URL:** https://api.cronlytic.com/prog
- **Connectivity:** โœ…
- **Authentication:** โœ…

## Job Information
- **Job Count:** 3
- **Can List Jobs:** โœ…

## Performance
- **Performance Rating:** Good

## Recommendations
- ๐Ÿ’ก Found 3 job(s). All systems appear to be working correctly.

Claude Desktop Integration

To use with Claude Desktop, add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "cronlytic": {
      "command": "python",
      "args": ["-m", "cronlytic_mcp_server.server"],
      "env": {
        "CRONLYTIC_API_KEY": "your_api_key_here",
        "CRONLYTIC_USER_ID": "your_user_id_here"
      }
    }
  }
}

To run virtual environment of python

{
  "mcpServers": {
          "cronlytic": {
        "command": "python",
        "args": ["-m", "src.server"],
        "cwd": "PATH/cronlytic-mcp-server",
        "env": {
          "VIRTUAL_ENV": "PATH/cronlytic-mcp-server/.venv",
          "PATH": "PATH/cronlytic-mcp-server/.venv/bin:${PATH}",
          "CRONLYTIC_API_KEY": "your_api_key_here",
          "CRONLYTIC_USER_ID": "your_user_id_here"
        }
      }
  }
}

Development

Project Structure

cronlytic-mcp-server/
โ”œโ”€โ”€ src/
โ”‚   โ”œโ”€โ”€ __init__.py              # Package initialization
โ”‚   โ”œโ”€โ”€ server.py                # Main MCP server implementation
โ”‚   โ”œโ”€โ”€ cronlytic_client.py      # Cronlytic API client wrapper
โ”‚   โ”œโ”€โ”€ tools/                   # Tool implementations
โ”‚   โ”‚   โ”œโ”€โ”€ __init__.py
โ”‚   โ”‚   โ””โ”€โ”€ health_check.py      # Health check tool
โ”‚   โ”œโ”€โ”€ resources/               # Resource implementations (Phase 4)
โ”‚   โ”œโ”€โ”€ prompts/                 # Prompt implementations (Phase 5)
โ”‚   โ””โ”€โ”€ utils/                   # Utility modules
โ”‚       โ”œโ”€โ”€ __init__.py
โ”‚       โ”œโ”€โ”€ auth.py              # Authentication handling
โ”‚       โ”œโ”€โ”€ errors.py            # Custom error classes
โ”‚       โ””โ”€โ”€ validation.py        # Input validation
โ”œโ”€โ”€ tests/                       # Test files (Phase 6)
โ”œโ”€โ”€ config/
โ”‚   โ””โ”€โ”€ example_config.json      # Example configuration
โ”œโ”€โ”€ requirements.txt
โ”œโ”€โ”€ pyproject.toml
โ””โ”€โ”€ README.md

Running in Development Mode

# Activate virtual environment (if not already active)
source venv/bin/activate

# Install in development mode (if not already done)
pip install -e .

# Set environment variables for testing
export CRONLYTIC_API_KEY="your_test_key"
export CRONLYTIC_USER_ID="your_test_user_id"

# Run with debug logging
python -m cronlytic_mcp_server.server --debug

# Run validation tests
python validate_phase1.py

# Format code (if you have development dependencies)
black src/
ruff check src/

# Type checking
mypy src/

Testing with MCP Inspector

# Install MCP Inspector
npm install -g @modelcontextprotocol/inspector

# Test the server
mcp-inspector python -m cronlytic_mcp_server.server

Error Handling

The server provides comprehensive error handling:

  • Authentication Errors: Clear guidance on credential issues
  • Connection Errors: Network and connectivity diagnostics
  • Validation Errors: Detailed field-by-field validation messages
  • API Errors: Proper error codes and user-friendly messages
  • Rate Limiting: Automatic retry with exponential backoff

Logging

Structured logging is provided at multiple levels:

# Normal operation
2025-01-27 10:30:00 - cronlytic_mcp_server.server - INFO - Cronlytic MCP Server initialized

# Debug mode
python -m cronlytic_mcp_server.server --debug

Roadmap

Phase 2: Basic CRUD Operations (Next)

  • create_job - Create new cron jobs
  • list_jobs - List all user jobs
  • get_job - Get specific job details
  • update_job - Update existing jobs
  • delete_job - Delete jobs permanently

Phase 3: Advanced Job Management

  • pause_job - Pause job execution
  • resume_job - Resume paused jobs
  • get_job_logs - Retrieve execution logs

Phase 4: Resources Implementation

  • Dynamic job resources
  • Cron template library
  • Real-time resource updates

Phase 5: Prompts & UX

  • Interactive job creation flows
  • Monitoring and troubleshooting guidance
  • User experience optimization

Phase 6: Testing & Documentation

  • Comprehensive test suite
  • Performance optimization
  • Complete documentation

Related Projects


Current Version: 0.1.0
Last Updated: Jun 2025

FAQ

Common questions

Discussion

Questions & comments ยท 0

Sign In Sign in to leave a comment.