mcp-memory-libsql
Related Servers
Alternatives to mcp-memory-libsql
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA high-performance MCP server providing long-term memory storage with semantic and keyword search capabilities, using SQLite and fastembed for sub-200ms queries.5GPL 3.0
- AlicenseNot gradedqualityCmaintenanceAn advanced MCP server providing RAG-enabled memory through a knowledge graph with vector search capabilities, enabling intelligent information storage, semantic retrieval, and document processing.14 npm47MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for managing persistent AI memory using hybrid search (keyword + semantic vector) with SQLite storage and offline-first local embeddings.-
- AlicenseNot gradedqualityCmaintenanceOpen-source MCP server that gives any LLM long-term memory using a knowledge graph and vector search hybrid. It stores entities, observations, and relationships, enabling semantic recall across sessions with automatic clustering and fail-loud infrastructure.51MIT
- AlicenseBqualityAmaintenanceAn MCP server that provides persistent semantic memory for LLMs by building a concept graph with vector search. It enables storing, linking, and retrieving concepts across conversations using Turso vector search and 256-dimensional embeddings.226PolyForm Noncommercial 1.0.0
- AlicenseAqualityCmaintenancePersistent memory MCP server for AI agents, using SQLite with hybrid keyword and semantic search for long-term memory storage.5Do What The F*ck You Want To Public
TDQS
Scored across 6 tools
Every tool has a clearly distinct purpose: create_entities and create_relations handle creation of different data types, delete_entity and delete_relation handle deletion of different data types, read_graph retrieves recent data, and search_nodes performs searches. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern using snake_case: create_entities, create_relations, delete_entity, delete_relation, read_graph, and search_nodes. The naming is predictable and uniform throughout the set.
With 6 tools, this server is well-scoped for a memory/graph database system. Each tool serves a clear and necessary function (create, delete, read, search) without being too sparse or bloated, fitting typical expectations for such a domain.
The toolset covers core CRUD operations for entities and relations (create, delete, read, search), but lacks explicit update tools for modifying existing entities or relations. Agents can work around this by deleting and recreating, but it's a minor gap in lifecycle coverage.