Skip to main content
Glama
jasona7

mcp-crontab-server

by jasona7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-crontab-server

No user-submitted related servers found.

    Related Servers

    • cronsense

      MrProLopstar
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to convert schedule text to cron expressions, describe cron in natural language, and compute upcoming run times.
      287 npm
      8
      MIT

    • cron-explainer

      IdoAzaCalls
      A
      license
      Not graded
      quality
      D
      maintenance
      Parses cron expressions, returns next fire times, and provides an English description.
      MIT

    • cron-check

      arhancanli
      A
      license
      A
      quality
      B
      maintenance
      Explains cron expressions in plain English, checks them for errors and gotchas, lists next run times in any time zone, and converts between Unix cron, GitHub Actions, Kubernetes, AWS EventBridge, Quartz and Spring dialects.
      3
      MIT

    • Cron Parser API

      Br0ski777
      A
      license
      Not graded
      quality
      D
      maintenance
      Parse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list/search target entries, add/remove modify entries, get_cron_logs retrieves logs, and the three expression tools (explain, validate, next_runs) each return different outputs. There is no overlap that would confuse an agent.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_crontab, search_crontab, add_cron_entry, etc.) with consistent snake_case. The exception is 'next_runs', which is a noun phrase rather than verb-first, and 'get_cron_logs' uses 'get' while others use different verbs, but the overall pattern is still readable.

    Tool Count5/5

    8 tools is well-scoped for a crontab manager: entry operations (list/search/add/remove), log retrieval, and cron expression utilities (explain/validate/next_runs). Each tool serves a distinct need, and the count is appropriate.

    Completeness4/5

    The surface covers the core workflows: viewing (list/search), modifying (add/remove), checking execution (logs), and handling expressions (explain/validate/next_runs). An update/edit tool is missing, which would be a minor gap, but re-adding after removal is a workaround.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources