Skip to main content
Glama

Related Servers

Alternatives to codex-lcm

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Centralizes verbatim local AI conversation history into a SQLite database and exposes it via an MCP server, enabling tools like Claude Code and Codex to retrieve exact context from other tools.
      1 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Collects session JSONL from Codex and Claude Code into local SQLite memory, exposed through MCP with tools for memory context, search, get, put, forget, sleep, and status.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables local-first personal knowledge management for Codex by turning conversations into a searchable archive, extracting durable facts, building a knowledge graph, and injecting relevant context into later sessions.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code sessions to automatically capture and retrieve architectural decisions, code changes, bug fixes, and configuration context across sessions using local SQLite storage and hybrid semantic/keyword search.
      57 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI assistant to keep every conversation verbatim in a local SQLite store and recall the most relevant past turns on demand, using hybrid keyword and embedding search plus time-awareness. Results are packed into a small token budget (2k–8k tokens) so long histories fit modest context windows, with secrets masked before storage.
      MIT

    TDQS

    B3/5.0

    Scored across 6 tools

    Disambiguation2/5

    lcm_grep and lcm_recall are nearly indistinguishable: both are described as lexical FTS5 search with literal substring fallback across messages and summaries. The remaining tools are distinct, but this overlap creates a real risk of misselection.

    Naming Consistency4/5

    All tools share the lcm_ prefix and snake_case convention, which is highly predictable. Most names are verb-like, though lcm_recent and lcm_status are descriptive/adjectival rather than action verbs.

    Tool Count5/5

    Six tools is well-scoped for a memory-database access server, covering expansion, recent activity, metadata, health, and search without excessive surface area.

    Completeness3/5

    The retrieval surface is fairly complete for reading and inspecting memory, including expansion and health status. However, there is no visible write/ingest operation, so agents cannot persist or update memories through this server.

    Maintenance

    ActivityStale
    ResponsivenessNo issues