memorix

★ 857

mcp-local-memory

★ 60

memorix vs mcp-local-memory

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

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

memorix: Memorix is a cross-agent memory bridge that prevents AI assistants from losing context across sessions and different development environments. It offers persistent local memory, workspace synchronization, and auto-generated project skills to enhance developer productivity.; 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.

TL;DR

memorixMemory & Context · ★ 857

Ensuring AI remembers past architectural decisions and conversations across sessions.

Read memorix full review →

mcp-local-memoryMemory & Context · ★ 60

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

Read mcp-local-memory full review →

Side-by-Side Comparison

Field

memorix

mcp-local-memory

Features

memorix

01Smart memory system with token-efficient progressive disclosure and hybrid search (BM25 + vector).

02Cross-agent workspace synchronization for configs, rules, skills, and workflows across multiple IDEs.

03Persistent knowledge graph with 9 observation types, compatible with MCP Official Memory Server.

04Interactive web-based Visual Dashboard with D3.js knowledge graph, observation browser, and retention panel.

05Auto-memory hooks for automatically capturing decisions, gotchas, and problem-solutions from coding sessions.

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

Use Cases

memorix

↳Ensuring AI remembers past architectural decisions and conversations across sessions.

↳Facilitating seamless knowledge transfer and collaboration between different AI agents/IDEs.

↳Preventing recurring bugs and pitfalls by automatically injecting 'gotchas' into AI context.

↳Synchronizing AI assistant configurations, rules, and skills across various development environments.

↳Automatically generating project skills and documentation for faster onboarding of new team members or agents.

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.

FAQ

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

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

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

The best choice depends on your use case. Choose memorix if Ensuring AI remembers past architectural decisions and conversations across sessions., and mcp-local-memory if Provide persistent and shared memory for AI agents in local environments..

Is memorix free or open source?

Yes, memorix is open source on GitHub (Apache-2.0).

Is mcp-local-memory free or open source?

Yes, mcp-local-memory 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 memorix →Alternatives to mcp-local-memory →memorix details →mcp-local-memory details →

TL;DR

Side-by-Side Comparison

Features

Use Cases

FAQ

Deploy on DigitalOcean

Related