mcp-local-memory

★ 60

remnic

★ 227

mcp-local-memory vs remnic

Q: Which is better, mcp-local-memory or remnic?

By GitHub stars, remnic has more community adoption, but the best choice depends on your specific use case.

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.; remnic: Remnic is an open-source, local-first memory and context management system designed for AI agents. It provides a unified, durable knowledge store that integrates with various AI tools, ensuring agents retain and recall relevant information across sessions without cloud dependencies.

TL;DR

mcp-local-memoryMemory & Context · ★ 60

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

Read mcp-local-memory full review →

remnicMemory & Context · ★ 227

Empowering AI agents to recall user identity, project details, and preferences across multiple sessions.

Read remnic full review →

Side-by-Side Comparison

Field

mcp-local-memory

remnic

Features

mcp-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

remnic

01Local-first, markdown-based memory storage with no cloud dependency.

02Unified memory store accessible by multiple AI agents and tools (e.g., OpenClaw, Claude Code, ChatGPT).

03Automatic knowledge extraction, distillation, and intelligent context injection into agent prompts.

04Sharp retrieval through hybrid search (BM25 + vector + reranking) with explainable provenance.

05Memory OS with namespaces for multi-tenancy, hot/cold tiering, and optional at-rest encryption.

Use Cases

mcp-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.

remnic

↳Empowering AI agents to recall user identity, project details, and preferences across multiple sessions.

↳Maintaining persistent context for debugging sessions and research tasks, preventing repeated effort.

↳Creating personalized support 'passports' (e.g., 'What Helps Me') for self-advocacy with human-governed sharing.

↳Enabling human-gated correction loops for agents to update their knowledge and learn from past failures.

↳Providing a unified and consistent knowledge base for collaboration among multiple AI agents.

FAQ

What is the difference between mcp-local-memory and remnic?

Both mcp-local-memory and remnic are in the Memory & Context category. mcp-local-memory has 60 stars, while remnic has 227 stars.

Which is better, mcp-local-memory or remnic?

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 remnic if Empowering AI agents to recall user identity, project details, and preferences across multiple sessions..

Is mcp-local-memory free or open source?

Yes, mcp-local-memory is open source on GitHub (MIT).

Is remnic free or open source?

Yes, remnic is open source on GitHub (MIT).

Cloud Infrastructure

Deploy on DigitalOcean

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

Claim $200 Free Credit

→

Alternatives to mcp-local-memory →Alternatives to remnic →mcp-local-memory details →remnic details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related