Self-host marm-memory
v2.60.1Local-first AI memory layer and MCP server for coding agents
- Stars
- 424
- Ports
- 8001 (HTTP MCP server), 8002 (Web Console)
lyellr88/marm-mcp-serverWhat is marm-memory?
marm-memory is a self-hosted persistent memory layer for AI coding agents implementing the Model Context Protocol. It gives agents like Claude Code, Codex, Cursor, and VS Code a shared private memory that persists across sessions. The server stores conversations, notes, and summaries in a local SQLite database with semantic embeddings and full-text search for fast hybrid recall. It also indexes codebases to build a code graph for symbol lookup and architecture analysis, and extracts a concept graph linking decisions, errors, and ideas across sessions. All 16 MCP tools work over both HTTP and STDIO transports. Installation options include pip, Docker, and Docker Compose, with managed profiles for solo, multi-agent swarm, and trusted deployments. A bundled web console offers a local UI for memory inspection, graph exploration, and client setup. The project is open source under Apache 2.0.
Should you self-host marm-memory?
marm-memory scores 53/100 on selfhost.directory (how scoring works) and ranks #26 of 120 in AI Assistant. It has 424 GitHub stars.
It shipped 10 stable releases in the past year. The latest, v2.60.1, came out on 12 October 2026. New versions land roughly every 1 days.
Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is Apache-2.0-licensed and written mostly in Python.
Its closest alternative on selfhost.directory is hermes-agent (89/100, 257 989 stars). It scores higher overall, so compare the two before you pick. See marm-memory vs hermes-agent side by side.
Features
- Automatic Indexing
- Code Graph
- Concept Graph
- Cross-Client Memory Sharing
- Distillation
- Hybrid Recall
- Local LLM integrationOptional, disabled by default
- MCP protocol support
- MCP Tools Suite
- Memory CompactionOptional, disabled by default
- Multi-Agent Swarm Support
- Notebook System
- Persistent memory
- Session Management
- Web Console
marm-memory README
FAQ
Can I back up my MARM memory?
Yes. The Console's System page takes point-in-time snapshots of the memory database while the server runs. For a full filesystem copy, stop MARM first, then back up the ~/.marm/ directory which holds databases and local state.
How does recall work?
MARM uses filter→rerank hybrid recall: FTS keyword/BM25 search handles exact terms first, semantic embeddings rerank those candidates by meaning, and a conservative temporal weighting step gives newer memories a modest boost when scores are close.
What is the concept graph and how do I use it?
The concept graph turns stored memories into a queryable knowledge graph. marm_concept_build extracts typed entities and relationships from memory content, and marm_concept_recall answers direct lookups or multi-hop traversals up to depth 5. Indexing is automatic with a 30-second debounce.
Can MARM use a local model?
Yes, optionally. MARM can send distillation proposals and code context answers to a local OpenAI-compatible model server. It is off by default, each request must opt in, and endpoints are loopback-only unless deliberately overridden.
What MCP tools does MARM provide?
MARM exposes 16 MCP tools on both HTTP and STDIO: 8 core memory tools (smart recall, logging, notebook, delete, summary, compaction, distillation), 6 code-graph tools (index, lookup, context, trace, architecture, impact), and 2 concept-graph tools (build, recall).
Does Docker require an API key?
Docker HTTP mode should use MARM_API_KEY because the server listens through a container network bridge. Docker STDIO mode does not need a key because it communicates over local process stdin/stdout.
What is the difference between HTTP and STDIO transports?
HTTP is better for shared memory servers with multiple agents and requires an API key when exposed through Docker or 0.0.0.0. STDIO is simpler for private local agent connections with no network port or API key required.
Which AI platforms work with MARM MCP?
MARM has been tested with Claude Code, Codex, Antigravity, Qwen CLI, Grok Build, Hermes, VS Code, Devin, Kiro, and Cursor. Any client supporting standard MCP HTTP or STDIO transports should be able to connect.
How is MARM different from built-in AI memory?
MARM provides user-owned SQLite database storage, works across MCP-compatible clients, offers explicit hybrid recall with structured logs, enables multiple agents to share the same memory store, and treats retrieved memory as context rather than higher-priority instruction.
More in Knowledge Management
maxkbSelf-hosted, open-source AI agent platform: build RAG knowledge-base chatbots, orchestrate workflows with MCP tools, and embed Q&A into your own apps.- memExA structured personal knowledge base inspired by zettlekasten and org-mode, designed for notes, contexts, and pipelines with multi-user support and privacy controls.
MemorwiseSelf-hosted NotebookLM alternative for document chat with any LLM. Drop in files/links — local RAG Q&A, knowledge graphs, flashcards, quizzes, audio. One command.
memory-osSelf-hosted, open-source memory stack for Hermes Agent: seven layers adding Qdrant vector search, SQLite fact storage with trust scores, and automatic context injection.
Memos WorkerSelf-hosted notes and knowledge base on Cloudflare Workers with D1, KV, R2, featuring Markdown editing, full-text search, Telegram integration, and themes.
minneSelf-hosted, open-source personal knowledge management app using a graph database to auto-connect notes, with AI-assisted extraction and chat interface.
mnemoSelf-hosted AI memory sidecar with persistent knowledge graph, entity extraction, and semantic retrieval for LLM apps — works with Ollama, OpenAI, Anthropic.
moonstoneSelf-hosted headless PKM server turning Obsidian, Logseq, Zim vaults into a REST API with PWA editor, applets, and background services.
MulmoClaudeSelf-hosted AI assistant platform with personal wiki, collections, and messaging bridges — powered by Claude Code, data stays local.
muse-brainMUSE Brain is a self-hosted relational memory system for AI agents with emotional texture and 33 MCP tools. Runs on Cloudflare Workers with Postgres or SQLite.
NexidionNexidion is an open-source, self-hosted knowledge base for sensitive data with multi-user vaults, hierarchical notes, version history, PDF ingestion, and an AI agent.
Nextcloud Notes✎ Distraction-free notes and writing
0 comments