Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"memex": {
"args": [
"<path from `memex mcp path`>"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Local-first second brain that connects to Claude via MCP. Notes are stored as plain Markdown and indexed with a local ML model, fully offline, no API keys, nothing leaves your machine.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@evan-moon/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 @evan-moon/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 search / writing
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
Production ready MCP server with real-time search, extract, map & crawl.
Use any LLMs (Large Language Models) for Deep Research. Support SSE API and MCP server.
Web and local search using Brave Search API
MCP Security Weekly
Get CVE alerts and security updates for io.github.evan-moon/memex and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Make Claude smarter about you.
npm install -g @evan-moon/memex
Make Claude smarter about you.
Local-first second brain that connects to Claude via MCP. Notes are stored as plain Markdown and indexed with a local ML model, fully offline, no API keys, nothing leaves your machine.
Claude is only as smart as what's in the conversation. Your decisions, your context, your thinking, invisible unless you paste them in every time.
You: What did we decide about the auth approach last sprint?
Claude: I don't have context from previous conversations...
You: What did we decide about the auth approach last sprint?
Claude: [memex · search_notes · "auth approach decision"]
Found 2 notes:
Auth Architecture Decision Apr 14 #auth #backend
─────────────────────────────────────────────────────
Chose JWT + refresh tokens over sessions. Rationale:
stateless design fits horizontal scaling plan.
Based on your April 14th note: you went with JWT +
refresh tokens. Tom also flagged keeping auth decoupled
from payment logic, separate bounded contexts.
Claude searches your notes before answering and saves insights at the end of every conversation, automatically, without being asked.
npm install -g @evan-moon/memex
Connect to Claude Code:
memex mcp install
That's it. On first run, the embedding model (~450MB) downloads once to ~/.memex/models/.
memex recall install
Turns retrieval from something Claude has to decide to do into something that just happens. Every prompt you type is semantically searched against your notes, and the top 3 titles are injected as context before Claude answers — the same way native memory works. Claude then pulls full notes with get_note when a title looks relevant.
A background daemon keeps the embedding model warm (~/.memex/recall.sock), so a lookup costs ~30ms instead of the ~1.5s a cold CLI search spends loading the model. It idles out after 2 hours.
Cost: ~200MB resident while warm, plus up to 3 note titles of context per prompt. Remove with memex recall uninstall.
multilingual-e5-base--from / --topast (immutable record), state (mutable plan), or rule (Claude behaviour guide). Past notes refuse updates; rule notes auto-inject into Claude's system prompt