launching soon — join the waitlist

Your markdown,
searchable by meaning.

Instant, private semantic search for your markdown — in your terminal and inside your AI agents. Describe what you're looking for; MegaMem finds the note.

100% local — no cloud, no API keys ~0.4 ms warm queries CLI + HTTP + MCP

Join the waitlist

Be first to hear when MegaMem launches. A quick confirm email, then the launch note — no spam, ever.

I am a… (optional — pick up to 5)

By joining, you agree to get the launch announcement and product updates from We Build Stuff (MegaMem) at this address. Questions: support@mega.ec. You can withdraw consent at any time — every subscriber email carries a one-click unsubscribe.

why hybrid

Keywords miss meaning.
Vectors miss anchors.

Ask for “that note about why we dropped SQLite” and keyword search finds nothing — the note never contains the word SQLite. Ask a pure vector index for an exact error string and it shrugs. MegaMem runs both, every time.

MegaMemKeyword searchPure vector search
Finds paraphrases (“why we dropped SQLite”)● Yes — embeddings● Only the words you type● Yes
Exact anchors — error strings, names, tickers● Yes — BM25● Yes● Often missed
Both signals, fused per query● BM25 + embeddings, RRF● One signal● One signal
Your documents leave your machine?● Never — 100% local● Depends on the tool● Depends on the tool
Warm query latency● ~0.4 ms● Varies● Varies
how it works

Init. Index. Ask anything.

One command sets up a repo — config, MCP registration and the first index. After that, search however you work.

1

megamem init

Scaffolds the config, registers MegaMem with your AI tools over MCP, and builds the first index of your markdown.

2

Index lives with the repo

Every repo gets its own .megamem/ index — auto-gitignored — and edits reindex in about 2 seconds, so results are never stale.

3

Search three ways

The CLI in your terminal, an HTTP service on :7823, or MCP tools — search, read, grep — inside your agent.

$ megamem search "why did we drop SQLite"
# 1 · notes/architecture-decisions.md — high confidence
# 2 · research/db-comparison.md — graduated format, 3 chunks
$ megamem grep "error: SQLITE_BUSY"
# exact anchors hit BM25 — paraphrases hit embeddings — both fused, ~0.4 ms
features

Built for people who live in markdown

Docs, notes, research archives, journals, tweet corpora — if it's text on your disk, MegaMem can answer questions about it.

100% local, fully private

Your documents and indexes never leave your machine. No cloud, no account, no API keys — a single 26 MB binary does everything.

~0.4 ms warm queries

Answers land in under a millisecond once the index is warm — fast enough that searching feels like remembering.

Hybrid on every query

BM25 keyword search and neural embeddings run together on every query, fused with Reciprocal Rank Fusion. Neither signal is a fallback.

Agent-native MCP

Cursor, Claude Code, Codex, Windsurf and VS Code query your notes through MCP tools — search, read, grep and more. One megamem init wires it up.

Per-repo indexes, always fresh

Each repo keeps its own index in a .megamem/ folder (auto-gitignored), and saving a file reindexes it in about 2 seconds.

Filters + token-saver formats

Frontmatter — dates, tags, authors — powers recency boosting and filters. Result formats like graduated and scan keep agent context lean, with confidence labels on results.

open source

The engine is on GitHub today

MegaMem is open source (MIT) — install it now, star the repo, kick the tires. The waitlist above is for launch announcements and what's next.

# one line — a single 26 MB binary
curl -fsSL https://raw.githubusercontent.com/webuildstuffio/megamem/main/install.sh | bash
$ megamem init # config + MCP registration + first index
faq

Questions, answered

What MegaMem is, how the search works and what the waitlist is for.

What is MegaMem?

MegaMem is instant, private semantic search for your markdown and text. Point it at any folder — docs, notes, research archives, journals — and ask natural-language questions. It answers in about 0.4 ms from the terminal, over HTTP, or inside your AI agents via MCP.

Is it really 100% local?

Yes. MegaMem is a single 26 MB binary that runs entirely on your machine. Your documents and indexes never leave it — there is no cloud, no account and no API key.

How is it different from grep or a vector database?

Keyword search only finds the words you type, and pure vector search can miss exact anchors like error strings and function names. MegaMem runs BM25 keyword search and neural embeddings on every query and fuses the two rankings with RRF, so paraphrases and exact strings both land.

Which AI tools can use it?

Anything that speaks MCP — Cursor, Claude Code, Codex, Windsurf and VS Code among them. Agents get search, read and grep tools (plus status, ingest, index and kg_query), and one command — megamem init — registers everything for you.

What does the waitlist get me?

Launch announcements and product updates by email — and a say in what ships next. Joining is free; we email a confirm link first (double opt-in), then the launch note when it lands. No spam, one-click unsubscribe in every email.

What does MegaMem cost?

The engine is open source under the MIT license — free to use, straight from GitHub. The waitlist is about launch news and what's next, not a paywall.

Your notes already
know the answer.

Join the waitlist and hear the moment MegaMem launches.

Join the waitlist