mcp-memory-libsql and memory-journal-mcp
Both tools appear to be competing implementations of persistent memory systems for the Model Context Protocol (MCP), offering similar core functionalities like semantic knowledge storage and session management.
About mcp-memory-libsql
spences10/mcp-memory-libsql
🧠 High-performance persistent memory system for Model Context Protocol (MCP) powered by libSQL. Features vector search, semantic knowledge storage, and efficient relationship management - perfect for AI agents and knowledge graph applications.
Implements relevance-ranked text search with fuzzy matching across entities, observations, and relations using libSQL's full-text capabilities, optimized to minimize token consumption in LLM prompts. Supports both local SQLite and remote Turso databases via environment configuration, with token-based authentication for remote access. Exposes standard MCP memory operations (create/update/delete entities and relations, relationship exploration) through a text-search interface designed for AI agent knowledge persistence.
About memory-journal-mcp
neverinfamous/memory-journal-mcp
MCP Server for AI Context + Project Intelligence. Overcome Disconnected AI Sessions with Persistent Project Memory, Automatic Session Briefing & Summation, Triple Search, Knowledge Graphs, GitHub Integration (Actions, Insights, Issues, Kanban, Milestones, and PRs), Automated Scheduling, 42 Tools, Tool Filtering, and HTTP/SSE & stdio Transport.
Persists project context across AI sessions using SQLite with full-text and semantic vector search (HuggingFace transformers + sqlite-vec), enabling agents to auto-brief from history and hand off context via structured session summaries. Provides 61 MCP tools organized in 10 groups including GitHub Commander for automated issue triage, PR review, and audit workflows, plus dynamic multi-repo routing via PROJECT_REGISTRY for managing multiple projects with a single server instance. Architecture emphasizes structured error handling with classification codes and recovery hints for agent reliability, backed by 96.7% test coverage and Alpine Docker deployment.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work