MCP Cron
About
MCP server for scheduling and running AI prompts, HTTP/webhook requests, and shell commands
Details
- Author
- jolks
- GitHub stars
- 24
- Downloads
- 435
- Categories
- Other, Automation
Jump to
- Schedule shell command, AI, or HTTP tasks using cron expressions
- AI tasks can use other MCP servers via a config file
- Manage tasks (add, list, run, update, remove) via MCP protocol
- Task execution with output capture and result history
- Task persistence across restarts using SQLite
- Multi-instance safe — multiple instances can share the same database
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP CronCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via npx -y mcp-cron and configure it in your MCP client's config file (e.g., ~/.cursor/mcp.json or Claude Desktop's config). The server supports two transport modes: HTTP (Streamable HTTP, default) and stdio. Key command-line arguments include --transport, --ai-provider, --ai-model, --db-path, and --prevent-sleep.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp cron": {
"mcp-cron": {
"command": "npx",
"args": [
"-y",
"mcp-cron"
]
}
}
}
}McpServers
{
"mcp-cron": {
"command": "npx",
"args": [
"-y",
"mcp-cron"
]
}
}MCP Cron
Model Context Protocol (MCP) server for scheduling and managing tasks through a standardized API. The server provides task scheduling capabilities supporting both shell commands and AI-powered tasks, all accessible via the MCP protocol.
Features
- Schedule shell command or prompt to AI tasks using cron expressions
- AI can have access to MCP servers
- Manage tasks via MCP protocol
- Task execution with command output capture
- Task persistence across restarts (SQLite)
- Multi-instance safe — multiple instances can share the same database without duplicate execution
- Support multiple isolated instances with different --db-path
Installation
npm (recommended)
npx -y mcp-cron
Claude Code
claude mcp add mcp-cron -- npx -y mcp-cron
Cursor / Claude Desktop
{
"mcpServers": {
"mcp-cron": {
"command": "npx",
"args": ["-y", "mcp-cron", "--transport", "stdio"]
}
}
}
Recommended Configuration
A more complete setup with AI provider, model selection, and sleep prevention:
{
"mcpServers": {
"mcp-cron": {
"command": "npx",
"args": [
"-y", "mcp-cron",
"--transport", "stdio",
"--prevent-sleep",
"--ai-provider", "anthropic",
"--ai-model", "claude-sonnet-4-5-20250929"
],
"env": {
"ANTHROPIC_API_KEY": "your-api-key"
}
}
}
}
Using LiteLLM
To route AI tasks through a LiteLLM proxy:
{
"mcpServers": {
"mcp-cron": {
"command": "npx",
"args": [
"-y", "mcp-cron",
"--transport", "stdio",
"--prevent-sleep",
"--ai-base-url", "https://litellm.yourcompany.com",
"--ai-model", "claude-sonnet-4-5-20250929"
],
"env": {
"MCP_CRON_AI_API_KEY": "sk-your-litellm-key"
}
}
}
}
> The --ai-model value should match a model name in your LiteLLM proxy config. LiteLLM exposes an OpenAI-compatible API, so --ai-provider can be omitted (defaults to openai). When a custom base URL is set, mcp-cron automatically uses the Chat Completions API instead of the Responses API. The Responses API is only used for direct OpenAI (api.openai.com) and Azure OpenAI (*.openai.azure.com) endpoints.
> See Command Line Arguments and Environment Variables for all available options.
Building from Source
Prerequisites
- Go 1.24.0 or higher```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
