Zettelkasten-based persistent memory for AI coding agents. Works with Claude Code, Cursor, VS Code Copilot, Codex, Windsurf & any MCP client. No vector DB — just markdown + git sync.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"memex": {
"args": [
"-y",
"@touchskyer/memex"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Persistent memory for AI coding agents. Your agent remembers what it learned across sessions.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@touchskyer/memex' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @touchskyer/memex against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / writing
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
MCP Security Weekly
Get CVE alerts and security updates for Memex and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Persistent memory for AI coding agents. Your agent remembers what it learned across sessions.
English | 中文 | 日本語 | 한국어 | Español

Every time your AI agent finishes a task, it saves insights as atomic knowledge cards with [[bidirectional links]]. Next session, it recalls relevant cards before starting work — building on what it already knows instead of starting from scratch.
No vector database, no embeddings — just markdown files your agent (and you) can read.
| Platform | Integration | Experience |
|---|---|---|
| Claude Code | Plugin (hooks + skills) | Best — auto-recall, slash commands, SessionStart hook |
| VS Code / Copilot | MCP Server | 10 MCP tools, zero config |
| Cursor | MCP Server | 10 MCP tools, zero config |
| Codex | MCP Server | 10 MCP tools, zero config |
| Windsurf | MCP Server | 10 MCP tools, zero config |
| Pi | Extension (custom tools + hooks) | 8 tools, auto-recall hook, slash commands |
| Any MCP client | MCP Server | 10 MCP tools, zero config |
All platforms share the same ~/.memex/cards/ directory. A card written in Claude Code is instantly available in Cursor, Codex, or any other client.
npm install -g @touchskyer/memexStep 1: Add memex to your editor
| Platform | Command |
|---|---|
| VS Code / Copilot | Search "memex" in VS Code Extensions — install and done, no extra setup |
| Claude Code | /plugin marketplace add iamtouchskyer/memex then /plugin install memex@memex |
| Cursor | First npm install -g @touchskyer/memex, then one-click install |
| Codex | npm install -g @touchskyer/memex && codex mcp add memex -- memex mcp |
| Pi | npm install -g @touchskyer/memex && pi install npm:@touchskyer/memex |
| Windsurf / others | npm install -g @touchskyer/memex, then add MCP server: command memex, args ["mcp"] |
That's it — no extra setup needed. The MCP tool descriptions tell your agent when to recall and retro.
| Platform | How |
|---|---|
| VS Code / Copilot | Extension auto-updates from marketplace |
| Claude Code | /plugin uninstall memex then /plugin install memex@memex |
| Pi | npm update -g @touchskyer/memex and re-copy pi-extension/index.ts |
| Cursor / Codex / Windsurf | npm update -g @touchskyer/memex |
All clients read and write the same ~/.memex/cards/ directory. Sync across devices with git:
Prerequisite: Auto-create requires GitHub CLI (
gh auth login). Or pass your own git remote URL to skip this, including GitLab and self-hosted GitLab remotes.
memex sync --init # auto-creates private memex-cards repo on GitHub
memex sync --init <repo-url> # or specify your own repo URL (no gh/glab CLI needed)
memex sync on # enable auto-sync after every write
memex sync # manual sync
memex sync off # disable auto-sync
For GitLab, create an empty private repository first, then pass its SSH or HTTPS remote URL. See the GitLab sync guide for examples.