Skip to main content
Glama
miles990

sqlite-memory-mcp

by miles990

Related Servers

Alternatives to sqlite-memory-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.
      15 npm
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.
      8
      1
      MIT
    • -
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent memory for AI assistants like Claude, storing and retrieving information across conversations using a local SQLite database.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to query and store memories from past conversations using FTS5 search and topic-based retrieval, with no API costs.
      267 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Persistent memory + FTS5 full-text search for Claude Code conversation history. Indexes ~/.claude/projects/ JSONL into SQLite, exposes 10 MCP tools (store/recall/search memories, browse sessions, get summaries) plus prompts. Includes a web UI for visual exploration
      10
      93 npm
      95
      MIT

    TDQS

    B3.1/5.0

    Scored across 23 tools

    Disambiguation4/5

    Tools are grouped into clear domains: context, memory, skill, and failure, which makes their purposes generally obvious. A few retrieval tools like memory_read, memory_list, and memory_search have overlapping connotations, but their descriptions specify distinct lookup modes.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case verb_noun pattern, such as memory_write, context_set, skill_register, and failure_record. Each domain uses predictable verbs, so the naming convention is uniform and scannable.

    Tool Count4/5

    23 tools is on the higher end and feels slightly heavy, but the server covers four distinct subdomains that each need CRUD, search, and stats operations. The count is reasonable given the combined scope, though it could be tightened.

    Completeness4/5

    Each core domain has solid coverage: create, read, list, search, and delete/update where expected. Minor gaps exist, such as no memory update, no single-key context delete, and no skill unregister, but agents can generally work around these.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues