Skip to main content
Glama
Sign In
ai-dememory

ai-dememory

by GonzaloTorreras
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ai-dememory

No user-submitted related servers found.

    Related Servers

    • enscribe

      Zalitygit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP-capable AI client to search and write a local-first personal memory store backed by one SQLite file, fusing FTS5 keyword and locally computed vector search over records and git-tracked markdown knowledge pages. An optional authenticated HTTP mode shares the same memory across agents and devices without any cloud dependency.
      MIT

    • synapse

      anshulyadav1976
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with a local, private Markdown-based memory vault and SQLite search. Enables agents to search, read, list, and traverse linked knowledge pages via MCP with zero external runtime dependencies.
      7
      9
      MIT

    • Mneme Memory MCP

      ethos-zero
      A
      license
      A
      quality
      B
      maintenance
      A local-first shared memory layer for MCP-aware agents like Claude, Codex, and Hermes, enabling persistent memory across chats and clients via Markdown files and SQLite FTS.
      6
      2
      MIT

    • agents-memory

      Lolaplex
      A
      license
      Not graded
      quality
      A
      maintenance
      A local markdown memory and cross-agent context engine for AI coding assistants. It provides an MCP server with tools to search, add, retrieve, and distill persistent memory across tools like Claude Code, Cursor, and Zed.
      37 PyPI
      5
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 74 tools

    Disambiguation4/5

    Most tools have distinct purposes with detailed descriptions, but the large number (74) creates some potential for confusion between closely related tools like acceptance_plan, acceptance_status, and acceptance_template. Overall, an agent can differentiate with careful attention.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'memory.' prefix plus snake_case with verb_noun structure (e.g., capture_import, conflict_dismiss). Even longer names like acceptance_packet_archive_retention_plan adhere to this pattern, making naming highly predictable.

    Tool Count2/5

    With 74 tools, the count is very high, exceeding the typical well-scoped range. While the server covers a complex domain (memory management), many tools are read-only planning variants, suggesting potential over-fragmentation that could overwhelm agents.

    Completeness4/5

    The tool set covers a wide range of operations: capture, acceptance, conflicts, review, recall, maintenance, search, secrets, scheduling, and more. However, there is a notable lack of tools for actual deletion or mutation of core memories (most tools are planning/status), which may limit direct action capabilities.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources