Create CRUD operations for serverless cron jobs through 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
The Cronlytic MCP Server enables AI agents and LLM applications to:
🎯 Final Achievement Summary:
📊 Key Metrics:
# 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
# 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 .
The server needs your Cronlytic API credentials to function. You can provide these in several ways:
export CRONLYTIC_API_KEY="your_api_key_here"
export CRONLYTIC_USER_ID="your_user_id_here"
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
}
python -m cronlytic_mcp_server.server --api-key "your_key" --user-id "your_id"
# 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
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.
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"
}
}
}
}
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
# 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/
# Install MCP Inspector
npm install -g @modelcontextprotocol/inspector
# Test the server
mcp-inspector python -m cronlytic_mcp_server.server
The server provides comprehensive error handling:
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
create_job
- Create new cron jobslist_jobs
- List all user jobsget_job
- Get specific job detailsupdate_job
- Update existing jobsdelete_job
- Delete jobs permanentlypause_job
- Pause job executionresume_job
- Resume paused jobsget_job_logs
- Retrieve execution logsThis project follows a structured development approach with clearly defined phases. Each phase builds upon the previous one to ensure stability and maintainability.
MIT License - see LICENSE file for details.
docs/
directory for detailed specificationsdocs/cronlytic-API-specification.md
Current Version: 0.1.0 Last Updated: Jun 2025