memex — Claude Code MCP server: memory and install
memex stores an agent’s findings in linked Markdown cards and brings related context into later sessions. It suits workflows that span multiple tasks.
claude mcp add --env MEMEX_HOME=<MEMEX_HOME> --transport stdio memex -- npx -y @touchskyer/memexWhat memex does
memex turns useful findings from completed tasks into separate Markdown cards. Before a later task, the server can retrieve related cards, so the agent can build on earlier work. Cards use bidirectional links, and the system works without a vector database or embeddings.
The shared store is ~/.memex/cards/, which lets Claude Code, Cursor, and Codex access the same memory. The MCP server exposes 12 tools; memex serve opens a timeline and link graph for browsing the cards. Node.js 18+ is required for Codex, Cursor, and other MCP clients.
Keep secrets, credentials, tokens, and exact secret-file contents out of cards and queries. memex filters some high-confidence secrets, but it cannot redact unsafe tool arguments already shown in the client transcript.
What it helps with
- carry agent knowledge across sessions
- retrieve cards related to a coding task
- inspect the graph of linked memories
- share cards across Claude Code, Cursor, and Codex
- sync the memory store through Git
Example prompts for the agent
- Save the decision about this database migration as a card and link it to related notes.
- Before changing authentication, search the memory for cards connected to this project.
- Inspect the card network and show orphaned cards, hubs, and conflicts.
How to install memex
Platform CLI
claude mcp add --env MEMEX_HOME=<MEMEX_HOME> --transport stdio memex -- npx -y @touchskyer/memexReplace <…> with your own values
Platform CLI
codex mcp add memex --env MEMEX_HOME=<MEMEX_HOME> -- npx -y @touchskyer/memexReplace <…> with your own values
Config file
{
"mcpServers": {
"memex": {
"command": "npx",
"args": [
"-y",
"@touchskyer/memex"
],
"env": {
"MEMEX_HOME": "<MEMEX_HOME>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"memex": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@touchskyer/memex"
],
"env": {
"MEMEX_HOME": "<MEMEX_HOME>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e MEMEX_HOME=<MEMEX_HOME> memex npx -y @touchskyer/memexReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about memex
How do I install memex in Claude Code?
Run claude mcp add memex -- npx -y @touchskyer/memex, then run claude mcp add --env MEMEX_HOME=<MEMEX_HOME> --transport stdio memex -- npx -y @touchskyer/memex.
What does memex do?
It stores an agent’s knowledge in Markdown cards, connects those cards with bidirectional links, and retrieves related context in later sessions. The shared cards live in ~/.memex/cards/.
Does memex need a vector database?
No. It uses Markdown files and bidirectional links instead of a vector database or embeddings.
