Engram
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@EngramRemember that my favorite pizza topping is pineapple"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Engram
Your memory, on your machine.
Every AI platform is racing to build "memory" — and locking it inside their own walls. Your context, preferences, and history end up trapped in one vendor's product, invisible and unportable. Engram is the opposite bet: an open, local-first memory layer that you own, that follows you across every tool.
Engram runs as a Model Context Protocol server, so any MCP-capable client (Claude Code, Claude Desktop, and more as they adopt the protocol) can read and write your memory. Everything stays on your machine — the store, the search, even the embedding model. Nothing leaves.
How it works
Local-first — a single SQLite file on your disk is the source of truth.
On-device embeddings — semantic search runs locally (bge-small); your memories are never sent to a third party.
Hybrid recall — keyword (FTS5) fused with semantic similarity, so it finds what's relevant, not just what shares words.
Stays coherent — flags related or contradicting memories on save instead of silently piling up duplicates.
You're in control — a built-in inspect UI to browse, edit, tag, import, and export everything you've stored.
Status
Early development. v1 is a local MCP server backed by SQLite, with hybrid (keyword + semantic) recall and local embeddings — nothing leaves your machine. See docs/plans for the design.
Related MCP server: GroundMemory
Tools
Tool | Purpose |
| Search your memory for relevant entries |
| Store a new memory |
| Browse stored memories |
| Edit an existing memory |
| Delete a memory |
Development
npm install
npm run build
npm startThe server speaks over stdio. Point an MCP client (e.g. Claude Code or Claude Desktop) at the built dist/index.js to connect:
claude mcp add engram -- node C:\Dev\Engram\dist\index.jsInspect UI
A local web view to read, edit, tag, and export your memories lives in ui/:
cd ui
npm install
npm run devIt reads the same store at ~/.engram/memory.db. Memories added or edited here are re-embedded by the server on its next start.
Storage
Everything lives in ~/.engram/ — memory.db (SQLite, source of truth) and models/ (the local embedding model). Set ENGRAM_DIR to use a different location.
License
MIT © Kalyan Gopalam
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kalyan-Deva/Engram'
If you have feedback or need assistance with the MCP directory API, please join our Discord server