Skip to main content
Glama
ethos-zero

Mneme Memory MCP

by ethos-zero

Related Servers

Alternatives to Mneme Memory MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local shared-memory MCP server for Claude, Codex, Hermes, and other MCP-aware agents, providing a durable memory layer with Markdown files and SQLite fact store.
      6
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A shared memory layer for AI agents — one memory.md synced across Claude Desktop, Cursor, Claude Code, OpenAI Codex, and any MCP client.
      4
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for persistent, cross-session, local-first memory for AI agents, storing memories as Markdown files with SQLite indexing for hybrid search.
      24
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for personal and shared memory with full-text search (SQLite FTS5) and outcome tracking, compatible with any MCP agent like Claude Code, Cursor, and Codex CLI.
      6 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local-first MCP server for durable agent memory using SQLite and FTS5, enabling knowledge graph storage, search, and recall for AI agents.
      20
      1
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add, list, remove, search, summary, update. There is no conceptual overlap; an agent can easily select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent 'memory_verb' pattern using snake_case. The naming is predictable and aids discoverability.

    Tool Count5/5

    Six tools is an ideal count for a focused memory server. Each tool addresses a specific need without bloat, covering core CRUD and search operations.

    Completeness4/5

    The tool surface covers add, read (list, search, summary), update, and delete. Missing a bulk operation (e.g., clear memory) is a minor gap but not critical for typical usage.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing