mcp-memory-service and memory-journal-mcp
These are complementary tools designed for different layers of agent memory architecture—one provides a general-purpose persistent memory service with REST API and knowledge graph consolidation for multiple agent frameworks, while the other specializes in session-aware project memory with GitHub integration and automatic context summarization for individual development workflows.
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 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