mcp-memory-service and purmemo-mcp
The first tool, `doobidoo/mcp-memory-service`, provides a persistent memory *service* for AI agent pipelines, while the second tool, `purmemo-ai/purmemo-mcp`, is an MCP *server* specifically for the `pūrmemo` AI conversation memory application, indicating they are ecosystem siblings where the latter likely relies on or implements the standards of the former or a similar MCP architecture.
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 purmemo-mcp
purmemo-ai/purmemo-mcp
MCP server for pūrmemo — AI conversation memory that works everywhere. Save and recall conversations across Claude Desktop, Cursor, and other MCP-compatible platforms.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work