mcp-local-memory logo
mcp-local-memory
★ 60
vs
dakera-deploy logo
dakera-deploy
★ 19

mcp-local-memory vs dakera-deploy

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.; dakera-deploy: Dakera Deployment provides production-ready infrastructure to deploy the Dakera AI agent memory platform across various environments like Docker, Kubernetes, or Helm. It offers persistent, session-aware, and cross-agent memory capabilities, including vector search, knowledge graphs, and session management, all within a self-hosted Rust binary with no external dependencies.

01

TL;DR

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

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

dakera-deploy logo
dakera-deployMemory & Context · ★ 19

Local development and testing of AI agents using in-memory storage or MinIO-backed persistence via Docker Compose or Devcontainers.

02

Side-by-Side Comparison

Field
mcp-local-memory logomcp-local-memory
dakera-deploy logodakera-deploy
Category
Memory & Context
Memory & Context
Stars
★ 60
★ 19
License
MIT
NOASSERTION
Install Command
npm install -g @beledarian/mcp-local-memory@2
git clone https://github.com/dakera-ai/dakera-deploy && cd dakera-deploy/docker && docker compose -f docker-compose.local.yml up -d
Updated
1mo ago
1d ago
Open Source
Yes
Yes
Tags
AI Agents, Memory Management, Knowledge Graph
AI Agents, Memory Management, Vector Database
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
dakera-deploy logodakera-deploy
01Agent-native memory platform purpose-built for AI agents requiring persistent, session-aware, and cross-agent memory.
02Comprehensive memory features: vector search, hybrid retrieval (BM25 + HNSW), knowledge graphs, session management, and built-in embeddings.
03Self-hosted Rust binary with zero external dependencies, ensuring data stays on your infrastructure and achieving high performance (88.2% on LoCoMo benchmark).
04Flexible deployment options including Docker, Docker Compose, Kubernetes with kubectl manifests or Helm charts, and VS Code Devcontainers.
05Production-ready features: high availability (HA) cluster mode with load balancing, configurable tiered storage, authentication, and integrated monitoring with Prometheus and Grafana.
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.
dakera-deploy logodakera-deploy
↳Local development and testing of AI agents using in-memory storage or MinIO-backed persistence via Docker Compose or Devcontainers.
↳Deploying a single-node, production-grade AI agent memory system with MinIO storage, caching, and health checks for staging or smaller production environments.
↳Establishing a high-availability (HA) cluster with multiple Dakera nodes and a Traefik load balancer for robust production environments.
↳Cloud-native production deployments of the Dakera memory platform using Kubernetes with `kubectl` manifests or Helm charts for scalability and orchestration.
↳Integrating observability into Dakera deployments with Prometheus and Grafana for monitoring request rates, latency, cache performance, and cluster health.
FAQ

FAQ

What is the difference between mcp-local-memory and dakera-deploy?
Both mcp-local-memory and dakera-deploy are in the Memory & Context category. mcp-local-memory has 60 stars, while dakera-deploy has 19 stars.
Which is better, mcp-local-memory or dakera-deploy?
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 dakera-deploy if Local development and testing of AI agents using in-memory storage or MinIO-backed persistence via Docker Compose or Devcontainers..
Is mcp-local-memory free or open source?
Yes, mcp-local-memory is open source on GitHub (MIT).
Is dakera-deploy free or open source?
Yes, dakera-deploy is open source on GitHub (NOASSERTION).
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