Skip to main content
Glama

Related Servers

Alternatives to Chronos Protocol

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Provides persistent project memory, task lists, time tracking, and shared rules and learned preferences so coding agents can recall decisions and conventions across sessions and coordinate multi-step work.
      19
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent project memory for AI coding agents, enabling context retention across sessions via event logging, briefing generation, and querying.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent project-scoped and cross-project memory during sessions, using local semantic search to surface relevant decisions, preferences, error patterns, and guidelines across sessions. It also optionally exposes an autonomous task queue that draws on that same stored context.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to keep persistent, bi-temporal knowledge graph memory across sessions and tools, automatically retiring superseded facts. It compiles provenance-cited, token-budgeted context bundles and supports point-in-time queries and integrity verification.
      7
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides long-term memory and a temporal knowledge graph for AI agents, enabling persistent memory and reasoning across sessions.
      33
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent, local-first memory so project decisions, preferences, and cross-project guidelines survive across sessions and can be retrieved by semantic search. Optionally also exposes a task queue for autonomous execution that draws on the same stored context.
      -

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools like 'check_time_reminders', 'create_time_reminder', 'get_current_time', and 'convert_time' each handle specific time-related tasks, while 'start_activity_log', 'end_activity_log', 'get_activity_logs', 'update_activity_log', and 'get_elapsed_time' form a complete activity logging lifecycle. There is no overlap in functionality that could cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case throughout. Examples include 'check_time_reminders', 'convert_time', 'create_time_reminder', 'start_activity_log', and 'update_activity_log'. This predictability makes it easy for agents to understand and use the tools without confusion from mixed conventions.

    Tool Count5/5

    With 9 tools, the count is well-scoped for the server's purpose of time management and activity logging. Each tool earns its place by covering distinct aspects such as time retrieval, conversion, reminders, and activity tracking. This number is neither too thin nor too heavy, fitting typical expectations for a focused domain.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for both time management and activity logging domains. For time, it includes creation, checking, conversion, and retrieval. For activities, it supports starting, ending, updating, retrieving, and calculating elapsed time. There are no obvious gaps or dead ends that would cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues