Skip to main content
Glama

Related Servers

Alternatives to Aletheia

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Local, cross-agent memory for AI coding agents using a single SQLite file, enabling persistent sessions and durable facts shared across multiple MCP-compatible tools.
    5 npm
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Provides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.
    8
    MIT
  • A
    license
    Not graded
    quality
    F
    maintenance
    Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.
    2
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    Gives every AI agent on a machine a shared, local-first long-term memory: 16 tools to save, search, edit and organize structured notes in one SQLite file, with attribution per client. Runs over stdio or localhost HTTP, so Claude Code, omp and any other MCP client recall the same facts, decisions and entities.
    16
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.
    13 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.
    3
    MIT

TDQS

A4.4/5.0

Scored across 13 tools

Disambiguation4/5

Most tools have clearly distinct purposes, with explicit guidance on when to use search vs. timeline vs. get_observations. A few pairs (search vs. fact_history, save_memory vs. work_state_write vs. add_rule) overlap slightly but are well-differentiated by their descriptions.

Naming Consistency3/5

The naming is readable but mixes verb_noun patterns (list_rules, add_rule, save_memory) with noun-only names (search, timeline, fact_history) and an unusual compound (session_start_context). The convention is not uniform, though the intent remains understandable.

Tool Count5/5

Thirteen tools is well within the ideal range for a memory server of this scope. Each tool appears to earn its place, covering retrieval, storage, rules, facts, and work state without excessive redundancy.

Completeness4/5

The surface covers search, retrieval, storage, dismissal/restoration, rules, facts, and work state—most of the memory lifecycle. Minor gaps exist, such as no explicit update/edit operation for memories or a way to permanently delete, but these may be intentional design choices.

Maintenance

ActivityMaintained
ResponsivenessNo issues