mcp-memory-service and mcp-memory-libsql
These are competitors offering alternative MCP-based persistent memory backends—both provide vector search and knowledge graph capabilities for AI agents, so users would select one based on preference for REST API architecture versus libSQL's embedded database approach.
About mcp-memory-service
doobidoo/mcp-memory-service
Open-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation.
Consolidates multi-agent memory using a knowledge graph with typed edges (causes, fixes, contradicts) and autonomous compression, accessible via REST API with ONNX-based embeddings that run locally. Implements Remote MCP support for browser-based claude.ai integration via Server-Sent Events, alongside traditional desktop MCP, with OAuth 2.0 authentication and self-hosted infrastructure (no cloud lock-in). Agent identity is tracked via `X-Agent-ID` headers for scoped retrieval, and conversation threading is preserved through `conversation_id` fields, enabling both shared memory across agent fleets and inter-agent messaging through semantic tag-based filtering.
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.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work