Skip to main content
Glama

Related Servers

Alternatives to Waystone

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI coding assistants to store and retrieve persistent long-term memory across sessions, remembering project preferences, build steps, and architecture decisions.
      4
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Provides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.
      16
      61 npm
      2
      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
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to share a persistent, local-first memory of architectural decisions, conventions, bug root causes, and session handoffs, searchable via full-text ranking, so context carries across tools and sessions without any cloud dependency.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.
      33 PyPI
      11
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent, context-rich memory of a codebase, including documentation and git history, enabling recall across sessions.
      105
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target distinct actions in the memory/project lifecycle, and descriptions clarify workflow roles. The only real ambiguity is between memory_entries and memory_recall, since both return memories, but their scope differs (all entries vs. effective memories for the bound project).

    Naming Consistency4/5

    Almost all tools follow a verb_noun pattern with snake_case, such as memory_publish, memory_retract, and project_init. The exception is memory_entries, which uses a noun phrase instead of a verb (e.g., list_memories would be more consistent), but the overall pattern remains predictable.

    Tool Count5/5

    Twelve tools is well-scoped for a memory-and-project management server. Each tool covers a distinct lifecycle action, and none feel redundant or excessive.

    Completeness5/5

    The memory lifecycle is well covered: publishing, recalling, previewing, superseding, retracting, rejecting, rebasing, reindexing, and listing entries. Project management includes listing, initializing, and binding, which covers the apparent core workflows without obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues