Skip to main content
Glama
Sign In
cronty-com

Cronty MCP

Official
by cronty-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Cronty MCP

No user-submitted related servers found.

    Related Servers

    • agentrem

      fraction12
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing structured reminders for AI agents, with persistent storage, full-text search, and cross-session support.
      6 npm
      1
      MIT

    • claude-cron

      frr149
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that allows AI coding assistants to schedule deferred tasks such as reminders, shell commands, and AI prompts, executing them as an OS daemon.
      8 npm
      MIT

    • AgentCron

      Noriget
      A
      license
      Not graded
      quality
      D
      maintenance
      A hosted remote MCP server that lets your AI agent schedule tasks for later — reminders, delayed webhook callbacks, and recurring jobs. Read-only by design.
      2 npm
      MIT

    • Agent Notifications

      777genius
      F
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI agents send desktop notifications during tasks, ask for attention, and report completion. Supports macOS, Linux, and Windows, with optional webhook delivery.
      825
      -

    • ddlpin

      shuxiuzhang53
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server for task management with deadlines, enabling AI assistants to add, update, complete, and snooze tasks. It integrates with a desktop sticky note and ntfy push notifications for reminders.
      MIT

    • mcp-os-notifications

      ekomac
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that lets LLM agents dispatch native OS notifications when a task finishes. It supports cross-platform desktop notifications, task tokens for updates, mobile bridges, and quiet hours.
      2
      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.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scheduling (recurring vs one-off), immediate push, time retrieval, and lifecycle management (delete, pause, resume, list). There is no ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., delete_schedule, get_current_time, send_push_notification). The naming is predictable and easy to understand.

    Tool Count5/5

    8 tools cover the core functionality of a notification scheduling server. The number feels well-scoped—not too few to miss essential operations, not too many to overwhelm.

    Completeness3/5

    Recurring schedule management is complete (create, list, pause, resume, delete), but there is no update tool and no way to view or cancel one-off scheduled notifications. This leaves notable gaps in the lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources