Stop re-explaining
yourself to every AI tool.
Portable, encrypted memory that follows you across AI coding agents.
Save context in Claude Code, recall it in Cursor. One command to install.
The Problem
Every AI tool is a silo
You explain your codebase to Claude Code. Then again to Cursor. Then again to Codex. Each tool forgets between sessions. None of them share what they learned.
Explain once. Remembered everywhere.
Memex is the shared memory layer between all your AI tools. Save context in one agent, recall it in any other.
Claude Code
Cursor
Codex
Windsurf
Memex
Shared encrypted memory
Copilot
Gemini
Any MCP Tool
How It Works
Two steps. Then forget about it.
One command. That's it.
Sets up encryption, registers with your AI tools, and auto-imports your existing configs.
$ npx memex-mcp init
✓ Encryption key generated
✓ Database created
✓ Claude Code registered
✓ Imported: CLAUDE.md, .cursorrules
Setup complete! Memex is ready.Your agent remembers from here.
No configuration. No manual saving. Your agent learns as you work and recalls what it needs.
// Monday — agent learns naturally
save_memory("Auth uses Clerk with JWT.
Routes go through middleware.ts.",
tags: ["auth", "architecture"])
// Tuesday — context is already there
recall_memories("auth setup")
→ "Auth uses Clerk with JWT..."Portability
Save in one tool. Recall in another.
save_memory(
"API uses REST with
/api/v1 prefix..."
){
content: encrypted,
tags: ["api", "arch"],
project: "my-app"
}encrypted · local
recall_memories(
"API conventions"
)
→ "API uses REST with
/api/v1 prefix..."Same memory. Any MCP-compatible tool. No copy-pasting. No config files to maintain.
Features
Built for how developers actually work
Auto-imports your configs
Detects .cursorrules, CLAUDE.md, .codex/instructions.md and imports them automatically. Re-syncs on every session.
Project-scoped
Memories are automatically organized by project via git root detection. No cross-contamination.
Full-text search
SQLite FTS5 with BM25 ranking. Instant, relevance-scored search across all your memories.
Tag-based organization
Tag memories with architecture, auth, debugging, api — then filter and recall by tag.
CLI tools included
memex status, memex memories list, memex export — manage your memory from the terminal.
Open source
MIT licensed. Audit every line. Contribute. Fork. It's yours.
Security
We can't read your data.
No one can.
Every memory is encrypted with AES-256-GCM before it touches disk. Your encryption key is derived locally and never transmitted. Even when cloud sync ships, only encrypted blobs leave your machine.
AES-256-GCM
Authenticated encryption with unique IVs per memory. PBKDF2 key derivation.
Local-first
Your encryption key never leaves your machine. Data stays on disk.
No data leaves your machine
No server, no cloud, no third party. Plaintext stays local, always.
Open source
MIT licensed. Read every line of the encryption code yourself.
Your Agent
"Auth uses Clerk with JWT..."
AES-256-GCM Encryption
key = PBKDF2(passphrase) | random
iv = crypto.randomBytes(12)
Stored on Disk
a4f8c2...e91b (encrypted blob)
+ iv + authTag
Plaintext never leaves your machine
Comparison
The only memory layer that checks every box
| Memex | Mem0 | Pieces | Copilot Memory | |
|---|---|---|---|---|
| Cross-agent (MCP) | ✓ | ✓ | ✕ | GitHub only |
| E2E Encrypted | ✓ | ✕ | ✕ | ✕ |
| Local-first | ✓ | Self-host | ✓ | ✕ |
| One-command install | ✓ | ✕ | ✕ | ✓ |
| Open source | ✓ | Partial | ✕ | ✕ |
| Free | ✓ | Freemium | Freemium | Paid |
Get started in 30 seconds
One command. Works with any MCP-compatible AI tool.
Coming soon
Cloud sync is next
E2E encrypted cloud sync. Your memories travel across machines — only encrypted blobs leave your device.
No spam. One email when it's ready.