Memex
Persist coding preferences and facts locally in SQLite so your agent remembers context across chats without sending memory to a cloud vendor.
Overview
Memex is an MCP server for the Build phase that stores local SQLite-backed memory so coding agents retain preferences across conversations.
What is this MCP server?
- Local SQLite memory store on your machine with cross-chat persistence
- OCI stdio package ghcr.io/kioie/memex:0.6.0 plus native install path
- MEMEX_DIR controls data directory (default ~/.memex; use /data in Docker)
- MEMEX_USER_ID scopes memories per user; MEMEX_HYBRID=1 enables vector retrieval fusion
- Privacy-first alternative to hosted memory SaaS for coding agents
- Server version 0.6.0
- Storage: local SQLite under configurable MEMEX_DIR
- Optional MEMEX_HYBRID=1 for hybrid vector retrieval fusion
Community signal: 1 GitHub stars.
What problem does it solve?
Coding agents forget project-specific preferences every new chat, forcing you to repeat stack choices and workflow rules.
Who is it for?
Privacy-conscious solo builders who want persistent agent memory on-disk while integrating via Docker OCI or native Memex installs.
Skip if: Teams that need multi-user cloud sync, enterprise audit trails, or zero local ops (Docker/volume management).
What do I get? / Deliverables
Connected agents read and write scoped memories in your local Memex database so context carries forward without a hosted memory account.
- Persistent scoped memory records on local disk
- Agent-retrievable project preferences across separate chat sessions
Recommended MCP Servers
Journey fit
Durable agent memory is core build-phase agent tooling— it keeps long-running solo projects coherent while you iterate on code. Agent-tooling subphase covers MCP servers that extend what Claude Code and peers remember between sessions.
How it compares
Local SQLite memory MCP, not a hosted vector database product or generic note-taking skill.
Common Questions / FAQ
Who is Memex for?
Indie developers using MCP coding agents who want durable, local preference memory without shipping data to a third-party cloud.
When should I use Memex?
During build and ongoing operate-style iteration whenever session resets erase conventions you already explained to the agent.
How do I add Memex to my agent?
Run ghcr.io/kioie/Memex:0.6.0 with stdio MCP, set MEMEX_DIR (and optional MEMEX_USER_ID or MEMEX_HYBRID=1), then register the server in Claude Code or Cursor.