Skip to main content
Glama
hb407033

Waystone

by hb407033
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Waystone

No user-submitted related servers found.

    Related Servers

    • evermemos-mcp-server

      wyh0626
      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

    • CastPlan MCP

      Ghostseller
      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

    • engrams

      stevebrownlee
      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.
      11
      Apache 2.0

    • Heimdall MCP Server

      lcbcFoo
      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.
      104
      Apache 2.0

    • ShackleAI Memory MCP

      shackleai
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory for AI coding tools, enabling AI assistants to store and recall project decisions, conventions, and context across sessions.
      26 npm
      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.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

    Resources