Skip to main content
Glama

Related Servers

Alternatives to MCP Cron Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A robust task scheduler server built with Model Context Protocol for scheduling and managing various types of automated tasks including shell commands, API calls, AI tasks, and reminders.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI tools to manage and operate the sched cron scheduler via the Model Context Protocol, including task scheduling, monitoring, and configuration.
      2 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI agents manage cron jobs through natural language — adding, listing, pausing, removing, running, and viewing logs of scheduled jobs with plain-English schedule parsing, automatic log capture, missed-run detection, and failure alerts.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that surfaces scheduled-job state and detects silent failures (exit 0 but no useful output) for cron, systemd timers, and OpenClaw schedulers, enabling AI agents to query job health and overdue status directly.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables creation and management of scheduled tasks with interval, cron, or one-time triggers. Persists tasks in SQLite and supports MCP sampling to automatically invoke AI agents when schedules trigger.
      5 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for scheduling and executing Claude Code CLI tasks via cron expressions, featuring a web dashboard and webhook support. It enables users to dynamically create custom MCP servers, manage recurring AI jobs, and track execution history with token and cost analytics.
      24
      MIT

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: add, list, remove, run, and status cover different aspects of cron job management. The descriptions are straightforward and prevent any confusion between tools.

    Naming Consistency5/5

    All tool names follow a consistent 'cron_verb' pattern (e.g., cron_add, cron_list), using snake_case throughout. This predictable naming makes it easy to understand and navigate the tool set.

    Tool Count5/5

    With 5 tools, this server is well-scoped for managing cron jobs, covering essential operations without being overly complex or sparse. Each tool serves a clear and necessary function in the domain.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for cron job management: add, list, remove, run, and status. There are no obvious gaps, allowing agents to handle all typical workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues