Skip to main content
Glama

Related Servers

Alternatives to mcp-memory

  • A
    license
    A
    quality
    C
    maintenance
    An MCP server that provides LLMs with full read/write access to an Open Knowledge Format (OKF) knowledge bundle, enabling structured, persistent long-term memory.
    11
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides persistent long-term memory for AI assistants with tag-based retrieval, wiki-style linking, and source references, storing memories as markdown files with SQLite index.
    1
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Provides persistent OKF memory for DeepSeek Harness by storing and indexing Markdown memories in SQLite FTS5, enabling agents to search, store, and export memories through MCP tools.
    257 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to maintain a persistent, queryable memory stored as user-owned Markdown files, with dual-channel retrieval (FTS5 and optional semantic search) and an audited write pipeline.
    11
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Persistent memory for AI agents enabling saving, searching, and managing knowledge across sessions with local markdown files.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents like Codex, Grok Build, and Antigravity to share persistent local memory, preferences, project context, tasks, and handoffs using Markdown and SQLite.
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables coding agents to store, search, and retrieve long-term memory as plain Markdown files with a disposable SQLite index, including note management, decision/bug tracking, and codebase symbol lookup via MCP.
    8
    MIT

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation3/5

memory_get_last and memory_retrieve overlap because both can retrieve the same system/last_memory record, and memory_update_last similarly overlaps with memory_store for that key. The AGENT DIRECTIVE text helps clarify intended usage, but the boundaries between generic and session-specific operations are not fully crisp.

Naming Consistency4/5

All tools share a consistent memory_ prefix and snake_case formatting, following a readable memory_<verb> pattern. Minor synonym inconsistency between retrieve/get and store/update keeps it from being perfectly uniform.

Tool Count5/5

Six tools is well-scoped for a memory server: generic CRUD plus session checkpointing. Each tool has a distinct role, and the specialized checkpoint pair adds clear value without bloating the surface.

Completeness5/5

The set covers the full memory lifecycle: store, retrieve, search, delete, and session checkpoint read/write. There are no obvious dead ends for the stated domain of persistent project memory.

Maintenance

ActivityMaintained
ResponsivenessWithin a week