Skip to main content
Glama

Related Servers

Alternatives to sill-ensoul

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent, cross-tool memory layer for AI coding agents via MCP, enabling storage and retrieval of decisions, preferences, and context across different tools and models.
      1 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent, shared memory for AI agents via MCP, enabling retrieval of relevant memories instead of loading entire context. Allows agents across projects, machines, and tools to share a single auditable, markdown-native brain.
      3
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides shared long-term memory for AI coding agents via MCP, allowing tools like Claude Code and Codex to store and retrieve distilled facts, notes, and conversation history to persist context across sessions.
      26 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent, multi-project memory for AI agents via MCP, enabling them to store and retrieve tasks, decisions, errors, checkpoints, and documentation while keeping context isolated by project.
      2
      MIT

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct action (create/list/delete agent, read/search/write wiki, append log), and descriptions clarify the one potentially confusing pair (agent_index vs wiki_read). The name agent_index could be misread as an agent list, but its description removes that ambiguity.

    Naming Consistency3/5

    Most wiki operations use a wiki_<verb> pattern, while agent lifecycle operations use <verb>_agent; this mixed ordering is readable but not uniform. agent_index is a noun-noun exception, and wiki_read vs wiki_write_concept is asymmetric. All names are snake_case and semantically clear.

    Tool Count5/5

    Eight tools is a well-scoped set for managing agent bundles and their knowledge wikis. Each tool covers a distinct need without redundancy, and the count is within the ideal range.

    Completeness4/5

    Core workflows are covered: create/list/delete agents, open/search/read concepts, write concepts, and append log entries. There is no direct way to update an agent's persona/index or delete an individual concept, but these are minor gaps that can be worked around via concept writes or log entries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues