Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Local-first second brain with semantic search. Markdown notes indexed by a local ML model.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"memex": {
"command": "npx",
"args": [
"-y",
"@evan-moon/memex"
]
}
}
}Run this in your terminal
claude mcp add memex -- npx -y @evan-moon/memexPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"memex": {
"command": "npx",
"args": [
"-y",
"@evan-moon/memex"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"memex": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@evan-moon/memex"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account evan-moon, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
memex
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 your apps:
memex mcp install
This registers memex with every MCP client on this machine — Claude, Claude Code, Codex, Cursor — by writing each one's own config file. Restart the clients afterwards.
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-baseMEMEX_RERANK=1), retrieves twice as many candidates and reorders them with bge-reranker-v2-m3. Worth ~+20pp hit@1 on the golden set, at ~1.8s per search — off by default because auto-recall and the CLI are built around instant lookups--from / --topast (immutable record), state (mutable plan), or rule (Claude behaviour guide). Past notes refuse updates; rule notes auto-inject into Claude's system promptsave_note warns when a semantically similar note already exists, nudging Claude to update rather than create[[Title]] syntax; get_note shows which notes reference itamends), so search flags the superseded note and points at the newest fix instead of returning a claim you already know is wrongmemex digest summarises notes saved in the last N days, grouped by folder.md files; works alongside existing vaultssqlite-vec at ~/.memex/memex.db# Add notes
memex add # interactive prompt (asks for layer) memex add --title "Note title" --content "..." --layer past memex add --title "Note title" --file ./note.md --layer state memex add --title "Note title" --content "..." --folder work/people/tom --layer past memex add --title "Note title" --content "..." -T typescript -T architecture --layer past
memex layer # distribution of past / state / rule memex layer state # move a note to a different layer
memex search "semantic search query" # multilingual memex search "knowledge management" --limit 10 # multilingual: matches Korean/Japanese notes too memex search "query" --tag typescript # filter by tag memex search "query" --from 2026-04-01 # notes since a date memex search "query" --from 2026-04-01 --to 2026-04-30
memex list # recent 10 notes memex list --limit 20 memex show memex tags # all tags with counts memex related # semantically related notes memex digest # last 7 days + signals + inferences memex digest --days 30 # summary of last 30 days
memex signals # detect un-synthesized patterns memex signals --type hidden_arc # one type only memex signals dismiss # triage (also: snooze) memex signals mint # print evidence bundle to synthesize memex signals mint --title "..." --summary "..." --confidence 0.7 memex inferences # list inferences (auto-flags stale) memex schedule # print cron/launchd snippet (no daemon)
memex edit memex delete memex delete --yes # skip confirmation
memex source add ~/Documents/My\ Notes # register a vault memex source list memex source remove ~/Documents/My\ Notes memex index # scan vault + all sources memex index --force # re-index everything memex reembed # re-embed with current model
memex config show memex config set vault-path ~/Documents/Second\ Brain
memex mcp install # register with every MCP client on this machine
memex recall install # search notes on every prompt, inject hits memex recall uninstall # remove the hook memex mcp path # print MCP binary path
memex mcp install
It writes each client's own config file and leaves the servers already in it alone. If a client still runs an older copy of memex, it gets repointed. memex mcp path prints the server path for a client memex does not know about yet.
| Tool | Description |
|---|---|
save_note | Save a note, requires layer, warns if a similar note already exists, surfaces flashbacks |
search_notes | Semantic search; supports category, tag, date_from, date_to filters; appends flashbacks for the top result |
list_notes | List recent notes |
list_tags | List all tags with note counts |
list_folders | List all folders with note counts |
get_note | Get full content and backlinks of a note by ID |
update_note | Update title or content. Refuses past notes (with [Amendment] suggestion) and rule notes (user-only) |
delete_note | Delete a note by ID |
get_signals | Deterministic un-synthesized patterns (hidden_arc / stale_state / dangling_link / tag_burst) |
update_signal_status | Triage a signal, dismiss or snooze |
list_inferences | List synthesized hypotheses (re-checks staleness first) |
get_inference | One inference with full provenance + change/delete markers |
mint_inference | Persist an approved hypothesis, requires explicit confirmation |
Inferences are kept separate from notes (excluded from search) and are cited as hypotheses, never facts. Detection stays deterministic; the only LLM step is synthesizing an inference's summary, which Claude does, never memex.
Every note is classified into one of three layers based on mutability:
| Layer | Meaning | Claude's permission |
|---|---|---|
past | Record of what happened, retros, meetings, decision rationale, debugging sessions | Append-only. update_note refuses, suggesting an [Amendment] note instead |
state | Current state or plans, project progress, roadmaps, a person's current role | Freely updatable |
rule | Behaviour guide for Claude, coding style, search policy | Claude is read-only. Only the user writes |
The CLI prints a colour-coded [past] / [state] / [rule] badge next to each note in list, search, and show.
save_note (MCP) and memex add (CLI) require an explicit layer. The classification rules are documented in the tool description so Claude picks correctly.projects/dev/herald → state, coding → rule, everything else → past. Migration is idempotent.rule notes are also auto-injected into the MCP server's instructions, see Rule layer auto-inject below.When you save a note or search, memex automatically surfaces older notes from a different folder that are semantically similar, "you wrote about this 124 days ago in a different context." Stored as system-generated backlinks (note_links.source = 'flashback'), separate from your [[wikilinks]] (source = 'wiki').
Tune via env:
| Env | Default | Behaviour |
|---|
| `MEMEX_FL
Only the beginning is shown; read the rest in the repo