Memex
Give your coding agent a Zettelkasten memory on disk with bidirectional links so context survives across sessions and tasks.
Overview
Memex MCP is a build-phase MCP server that provides a Zettelkasten agent memory with bidirectional links stored under a configurable local MEMEX_HOME directory.
What is this MCP server?
- Zettelkasten-style cards with bidirectional links for agent recall
- Local data directory configurable via MEMEX_HOME (default ~/.memex)
- stdio npm package @touchskyer/memex v0.1.8 for MCP hosts
- Bridges note-taking patterns builders already use with automated agent read/write
- Supports long-horizon solo projects where chat context windows are the bottleneck
- Package version 0.1.8; transport stdio via @touchskyer/memex
- Environment variable MEMEX_HOME for custom data directory
- Repository: github.com/iamtouchskyer/memex
Community signal: 232 GitHub stars.
What problem does it solve?
Agents forget prior decisions and research because everything lives in ephemeral chat context instead of a linked note graph.
Who is it for?
Solo builders running long Claude Code or Cursor projects who want Obsidian-like linking without manual copy-paste into every prompt.
Skip if: Teams needing cloud multiplayer knowledge bases, compliance audit trails, or heavy semantic search over terabytes of data.
What do I get? / Deliverables
After registration, your agent can create, link, and retrieve Memex cards so project knowledge compounds across sessions.
- On-disk Memex card store with bidirectional links accessible to the agent
- Repeatable memory reads/writes across coding sessions without re-explaining context
Recommended MCP Servers
Journey fit
Persistent structured memory is installed while you are building agent workflows, then pays off during operate iteration and grow content reuse. Agent-tooling is the canonical shelf because Memex is an MCP-backed memory layer for LLM hosts, not a production monitoring stack.
How it compares
Local Zettelkasten MCP memory, not a hosted vector database or RAG pipeline product.
Common Questions / FAQ
Who is Memex MCP for?
Developers and indie founders who use MCP-enabled coding agents and want structured, linkable long-term memory on their own machine.
When should I use Memex MCP?
Adopt it during build when you define agent workflows, and keep using it in operate as you iterate so architecture notes and debugging findings stay linked.
How do I add Memex MCP to my agent?
Install @touchskyer/memex from npm, set MEMEX_HOME if you want a custom data path, add a stdio MCP server entry in Claude Code or Cursor, and restart the host.