mcp-local-memory

★ 60

state-memory-mcp

★ 48

mcp-local-memory vs state-memory-mcp

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

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.; state-memory-mcp: @putervision/state-memory-mcp is a zero-infrastructure, deterministic Model Context Protocol (MCP) server designed to provide AI coding assistants with a structured, persistent SQLite graph for tracking workflow state. It offers efficient context management, reduces latency by offloading to a local database, and supports multi-agent collaboration with a shared blackboard.

TL;DR

mcp-local-memoryMemory & Context · ★ 60

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

Read mcp-local-memory full review →

state-memory-mcpMemory & Context · ★ 48

Providing persistent workflow state to AI coding assistants like Cursor and Copilot

Read state-memory-mcp full review →

Side-by-Side Comparison

Field

mcp-local-memory

state-memory-mcp

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

state-memory-mcp

01Deterministic State Memory & Compact TaskSlices for fast evaluation

02Efficient Context Management & Decision Thresholding to prevent graph bloat

03Multi-Agent Blackboard for shared context and parallel subagent updates

04100% Local & Private architecture, ensuring all state stays within your workspace

05Interactive 3D Visualizer for graph exploration

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.

state-memory-mcp

↳Providing persistent workflow state to AI coding assistants like Cursor and Copilot

↳Managing context and decision-making for autonomous agents

↳Facilitating multi-agent collaboration on complex tasks with a shared context store

↳Auditing and tracing agent activities with a tamper-evident event ledger

↳Improving agent efficiency and reducing latency in task retrieval and context processing

FAQ

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

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

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

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 state-memory-mcp if Providing persistent workflow state to AI coding assistants like Cursor and Copilot.

Is mcp-local-memory free or open source?

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

Is state-memory-mcp free or open source?

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

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related