Mengram – Open-Source Memory Layer for AI Agents
Persistent memory across Claude Code, Cursor, and ChatGPT. Mengram stores facts, episodes, and procedures that survive every /clear.
TL;DR
TL;DR: Mengram is an open-source memory layer for AI agents. It stores facts, event episodes, and procedural workflows that survive every
/clear— one memory shared across Claude Code, Cursor, Codex, and ChatGPT.
Source and Accuracy Notes
⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.
- Project page: mengram.io
- Source repository: github.com/alibaizhanov/mengram
- License: Apache 2.0 (verified via LICENSE file)
- Docs: mengram.io/docs
- PyPI package: pypi.org/project/mengram-ai
- HN launch thread: news.ycombinator.com/item?id=47412780
What Is Mengram?
AI agents forget everything after each conversation. Clear your Claude Code session and every learned preference, tech stack detail, and workflow is gone. Mengram fixes that by maintaining a persistent memory store your agents query at runtime.
Mengram stores three types of memory:
- Facts — static knowledge (“I use Python and deploy to Railway”)
- Episodes — events and interactions (“deployment failed on 2026-07-28 due to missing env var”)
- Procedures — workflows that evolve from failures (“to deploy, always check env vars first”)
Agents search this memory on every query. The result is continuity that survives /clear, context resets, and new sessions.
Setup Workflow
Step 1: Install
pip install mengram-ai
npm is also available:
npm install mengram-ai
Step 2: Get an API key
Sign up at mengram.io/#signup for a free key.
Step 3: Add your first memory
from mengram import Mengram
m = Mengram(api_key="om-...")
m.add([{"role": "user", "content": "I use Python and deploy to Railway"}])
Step 4: Search and ask
m.search("tech stack") # → facts
m.ask("what's my tech stack?") # → synthesized answer + citations
m.episodes(query="deployment") # → events
m.procedures(query="deploy") # → workflows learned from failures
Step 5: Agent install in one prompt
Paste this into any agent (Claude Desktop, Cursor, Codex, Claude Code, Windsurf):
Install Mengram for me. Fetch the canonical install guide at
https://mengram.io/agent-install.txt and follow it precisely.
My email is YOUR_EMAIL_HERE.
The agent fetches the install guide, installs the SDK, configures the MCP server, and verifies round-trip — no manual terminal work required.
Key Features
| Feature | Details |
|---|---|
| Multi-agent | One memory store shared across Claude Code, Cursor, Codex, ChatGPT |
| Memory types | Facts, episodes (events), procedures (evolved workflows) |
| Multilingual | 23 languages — ask in Russian, Chinese, Spanish, Japanese |
| Embeddings | Cohere multilingual embeddings + rerank |
| Agent install | One-prompt setup inside any compatible AI tool |
| MCP server | Configurable via agent install guide |
| License | Apache 2.0 (open-source) |
| Local try mode | mengram try — works offline, nothing leaves your machine |
Practical Evaluation Checklist
- [ ]
pip install mengram-aisucceeds - [ ]
mengram tryruns locally without an API key - [ ] Free API key obtained from mengram.io
- [ ]
m.add()stores a fact andm.search()retrieves it - [ ]
m.ask()returns a synthesized answer with citations - [ ] Agent install prompt works in Claude Code or Cursor
- [ ] Memory persists across a
/clearin Claude Code
Security Notes
- The local
mengram trymode requires no API key and makes no network calls - API key is required only when using cloud sync and retrieval features
- Mengram stores memory facts on their servers — review their privacy policy before storing sensitive project details
- MCP server configuration requires outbound HTTPS access to mengram.io
FAQ
Q: How is this different from Kinic or MemoryGate? A: Mengram organizes memory into three distinct types (facts, episodes, procedures) and emphasizes cross-agent sharing — the same memory is available in Claude Code, Cursor, Codex, and ChatGPT simultaneously. It also supports a fully offline “try” mode.
Q: Is there a free tier?
A: Yes. A free API key is available at mengram.io/#signup. The mengram try local mode requires no key at all.
Q: Does it work with self-hosted models? A: Mengram uses Cohere embeddings for retrieval. The agent-side SDK works with any LLM that calls the Mengram API. Self-hosted model compatibility depends on how the agent is configured.
Q: What languages are supported? A: 23 languages via Cohere multilingual embeddings — including English, Russian, Chinese, Spanish, Japanese, and more.
Q: Can I self-host Mengram? A: The core SDK is open-source (Apache 2.0). The hosted memory store is a SaaS product. Self-hosting the full stack is not documented in the current README.
Conclusion
Mengram solves the memory problem that every AI agent user hits eventually: you spend 20 minutes teaching Claude Code your project’s quirks, then /clear wipes it all. The fact/episodes/procedures taxonomy is more structured than a simple vector store, and the cross-agent sharing means your memory works everywhere, not just in one tool.
The one-prompt agent install is the killer feature for power users — paste it into any session and the agent handles the setup itself.
Source last checked: 2026-07-29
Related Posts
ai-setup
Recall – Persistent Memory for Claude Code via MCP Hooks
Recall gives Claude Code a permanent memory store that survives session restarts and context compaction. Four hooks capture and restore context automatically — with cloud SaaS or self-hosted options.
2/28/2026
dev-tools
Dulus Terminal Agent Setup Guide
Set up Dulus as a terminal AI agent with native and Docker paths, installer profiles, WebChat ports, repo safety checks, and shell-access risks.
5/28/2026
dev-tools
OpenSquilla Agent Gateway Setup Guide
Set up OpenSquilla with uv, onboarding, OpenRouter env keys, gateway runtime, Git LFS model files, and migration paths from other agents.
5/28/2026