Managing Cronicle Scheduler

Name: Managing Cronicle Scheduler
Author: wangjunneil

@wangjunneil

リポジトリ

Managing Cronicle Scheduler について

概要はまだありません

基本情報

カテゴリ

その他

トランスポート

stdio

公開者

wangjunneil

投稿者

Wang Calvin

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "managing-cronicle": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/managing-cronicle-scheduler",
        "run",
        "managing-cronicle-scheduler"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Managing Cronicle Scheduler?

Managing Cronicle Scheduler is an MCP server built with FastMCP that provides API tools for the Cronicle cron-like scheduling system, enabling interaction through MCP clients like Cherry Studio, Claude Desktop, and Cursor.

How to use Managing Cronicle Scheduler?

Set environment variables (CRONICLE_BASE_URL, CRONICLE_API_KEY, and optional defaults) in a .env file or inject them directly via the MCP client configuration. Run the server with uv run managing-cronicle-scheduler (default stdio transport) or for HTTP/SSE use the --transport flag.

Key features of Managing Cronicle Scheduler

15 exposed tools for scheduling and job management
Supports stdio and HTTP/SSE/Streamable HTTP transports
Written in Python, requires Python ≥ 3.11 and uv

Use cases of Managing Cronicle Scheduler

Create, update, delete, and view cron events programmatically
Run one-shot tasks that auto-disable after execution
Monitor active jobs, job history, and scheduler master state

FAQ from Managing Cronicle Scheduler

What tools does Managing Cronicle Scheduler expose?

It exposes tools like get_schedule, get_event, create_event, update_event, delete_event, run_event, get_job_status, abort_job, and more – covering event CRUD, job control, and master state management.

What are the runtime requirements?

Python 3.11 or higher and the uv package manager are required.

How do I configure the API connection?

Set CRONICLE_BASE_URL and CRONICLE_API_KEY (32‑character hex) as environment variables. Optional defaults (CRONICLE_DEFAULT_CATEGORY, CRONICLE_DEFAULT_TARGET, CRONICLE_DEFAULT_PLUGIN) can be overridden per call.