mcp-local-memory logo
mcp-local-memory
★ 60
vs
daimon-memory logo
daimon-memory
★ 14

mcp-local-memory vs daimon-memory

mcp-local-memory: mcp-local-memory is a local-first MCP server designed to provide AI agents with shared, durable memory without relying on Docker or cloud services. It achieves this through a powerful combination of hybrid semantic search, SQLite FTS5, and a structured knowledge graph, supporting features like temporal recall and adaptive ranking.; daimon-memory: Daimon-memory is a self-hostable memory backend for AI agents, storing typed records in PostgreSQL with Qdrant as a semantic index. It provides fast, cheap, and reproducible hybrid keyword + vector search recall without an LLM in the recall path.

01

TL;DR

mcp-local-memory logo
mcp-local-memoryMemory & Context · ★ 60

Provide persistent and shared memory for AI agents in local environments.

daimon-memory logo
daimon-memoryMemory & Context · ★ 14

Providing persistent, shared memory for AI agents across different tools.

02

Side-by-Side Comparison

Field
mcp-local-memory logomcp-local-memory
daimon-memory logodaimon-memory
Category
Memory & Context
Memory & Context
Stars
★ 60
★ 14
License
MIT
MIT
Install Command
npm install -g @beledarian/mcp-local-memory@2
git clone https://github.com/wakbijok/daimon-memory && cd daimon-memory && ./install.sh --yes
Updated
1mo ago
2mo ago
Open Source
Yes
Yes
Tags
AI Agents, Memory Management, Knowledge Graph
AI Agents, Memory, Persistence
03

Features

mcp-local-memory logomcp-local-memory
01Shared memory across multiple AI agents
02Hybrid semantic and keyword recall
03Structured knowledge graph for context management
04Temporal memory recall with natural language dates
05Adaptive memory ranking based on multiple factors
daimon-memory logodaimon-memory
01Persistent and typed memory for AI agents
02Deterministic and LLM-free recall using hybrid keyword + vector search
03Self-hostable backend using PostgreSQL for canonical storage and Qdrant for semantic indexing
04Single-subject memory space shared across multiple AI tools
04

Use Cases

mcp-local-memory logomcp-local-memory
↳Provide persistent and shared memory for AI agents in local environments.
↳Build knowledge bases and manage context for complex AI applications.
↳Facilitate local-first AI agent development and testing without external dependencies.
↳Serve as a centralized memory server for distributed AI agent systems via HTTP/SSE.
daimon-memory logodaimon-memory
↳Providing persistent, shared memory for AI agents across different tools.
↳Maintaining consistent personas and operating disciplines for AI agents.
↳Storing and retrieving AI agent decisions, lessons, incidents, and reminders.
↳Integrating memory capabilities with existing AI agent platforms like Claude Code, Codex, and Hermes.
FAQ

FAQ

What is the difference between mcp-local-memory and daimon-memory?
Both mcp-local-memory and daimon-memory are in the Memory & Context category. mcp-local-memory has 60 stars, while daimon-memory has 14 stars.
Which is better, mcp-local-memory or daimon-memory?
The best choice depends on your use case. Choose mcp-local-memory if Provide persistent and shared memory for AI agents in local environments., and daimon-memory if Providing persistent, shared memory for AI agents across different tools..
Is mcp-local-memory free or open source?
Yes, mcp-local-memory is open source on GitHub (MIT).
Is daimon-memory free or open source?
Yes, daimon-memory is open source on GitHub (MIT).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related