MegaMemory
A persistent-memory MCP server for coding agents: a graph of a project's concepts, architecture and decisions that survives across sessions
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Reads project code and writes a local database
- Downloads an embedding model on first run
Install
Manual install
npm install -g megamemory
megamemory installThe interactive installer asks for your editor and sets up the server and commands.
This is third-party code. Review the repository files before installing.
What it does
The server gives a coding agent memory that lives across sessions. The agent reads the code itself, describes concepts in its own words and writes them into a graph, then queries what it needs before a new task. The model is the indexer: there is no syntax parsing or static analysis, and it stores concepts such as features, modules, patterns and decisions rather than code symbols. All data sits in a local SQLite database in the project directory, and embeddings run in process. It installs into several editors with one command.
Who it is for. For developers who want an agent to remember a project's architecture and decisions across sessions.
Good fit when
- The agent forgets project context between sessions
- You want to store decisions and patterns, not just code
- You need semantic search over accumulated project concepts
Not a fit when
- You need syntax parsing and a precise index of code symbols
- You cannot keep a local database in the project directory
Example request
Remember this project's key architecture decisions and check them before the next taskLimitations
The model itself fills the memory, so the quality of the graph depends on how the agent describes concepts. There is no syntax parsing or static analysis, and no precise index of code symbols. It needs Node 18 or newer, and on first run it downloads an embedding model of about twenty three megabytes. Data is stored locally in SQLite in the project directory.
How to disable. Remove the MegaMemory entry from your MCP client config and uninstall the global megamemory package via npm.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Reads project code and writes a local database
- Downloads an embedding model on first run
README in short
The README presents MegaMemory as an MCP server that gives a coding agent a persistent knowledge graph of the project. The loop is simple: orient, work, update the memory. The model is the indexer, it stores concepts rather than code symbols, and everything lives in SQLite in the project directory. Installation is via npm install -g megamemory and an interactive megamemory install with targets for opencode, Claude Code, Antigravity and Codex. There is a web graph explorer. MIT licensed.
FAQ
Do I need paid keys?
No. Embeddings run in process and the model downloads automatically on first run; no paid keys are needed.
Where is data stored?
In a local SQLite database inside the project directory, one file per project.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything