mcp-local-memory

★ 60

memo

★ 24

mcp-local-memory vs memo

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

By GitHub stars, mcp-local-memory 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.; memo: Memo provides a 100% local, persistent, and searchable memory solution for AI coding agents, eliminating amnesia across sessions. It uniquely offers token-efficient context management, historical querying, contradiction detection, and autonomous maintenance, saving costs and improving agent performance.

TL;DR

mcp-local-memoryMemory & Context · ★ 60

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

Read mcp-local-memory full review →

memoMemory & Context · ★ 24

Providing continuous memory and context for AI coding agents across multiple sessions to prevent 'amnesia'.

Read memo full review →

Side-by-Side Comparison

Field

mcp-local-memory

memo

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

memo

01100% local, persistent, and searchable memory for various AI coding agents (e.g., Claude Code, Cursor), requiring no cloud or external databases.

02Token-efficient context management designed to reduce overhead and save costs for AI interactions.

03Time-machine capability to query knowledge as it was at any historical point, aiding in understanding past decisions.

04Contradiction radar that detects and helps resolve conflicting facts within the knowledge corpus.

05Autonomous nightly maintenance pipeline to optimize memory, resolve conflicts, and pre-warm embeddings.

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.

memo

↳Providing continuous memory and context for AI coding agents across multiple sessions to prevent 'amnesia'.

↳Storing and retrieving important decisions, facts, or project-specific knowledge for AI agents.

↳Analyzing the evolution of project knowledge and understanding the rationale behind past decisions using historical queries.

↳Managing changing project requirements by detecting and resolving contradictions in stored knowledge.

↳Enhancing AI agent responses by injecting relevant, token-optimized memory before model answers.

FAQ

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

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

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

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 memo if Providing continuous memory and context for AI coding agents across multiple sessions to prevent 'amnesia'..

Is mcp-local-memory free or open source?

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

Is memo free or open source?

Yes, memo 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 memo →mcp-local-memory details →memo details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related