Building a Second Brain Claude Can Actually Search
Most attempts at a second brain fail at the same point: the notes exist, but finding the right one six months later takes longer than working the answer out again. The Brain add-on for MCP Self-hosted takes a different route. Your notes live in a markdown vault on your own server, and Claude searches, reads and writes them for you.
This post covers how the vault works, how search finds things, why Brain has Can make changes on by default, and how versioning keeps that safe.
What is a second brain in MCP Self-hosted?
It is a folder of markdown files, the vault, plus ten tools that let Claude work with it: read, write, append, list, search, move, delete, describe a folder, reindex, and show history. The files are plain markdown on disk, so you can open, edit and back them up with any tool you like. Nothing is locked in a database.
Claude uses the vault the way you would ask a colleague with a good filing system: “Save the decision from today’s call under projects/pricing” or “What did we agree with the supplier about delivery times?”
Why is Can make changes for Brain by default?
Every other MCP Self-hosted tool starts read-only, because looking something up carries less risk than changing it. Brain is the exception. A second brain that Claude can only read is a slower version of the notes app you already have. It earns its place when Claude can save things as you work.
The default is not a requirement. The mode is set per seat on the Seats tab of your license. A read-only seat gets only the read tools: read, list, search and history. That suits a colleague who should look things up but not change them.
How do you set up the vault?
The download bundle already does most of the work of setting up a second brain. It contains an empty vault/ folder that is mounted into the container at /vault, and VAULT_PATH points there. Because the folder lives on the host, the vault survives container restarts and every ./mcp-update.sh run.
Two optional settings shape how it behaves:
VERSIONING_ENABLED=true
# INDEX_MAX_AGE_DAYS=7Put them in .env or under the Tools tab of your license, then refresh the license. The Brain MCP setup guide has the full list of steps.
How does Claude search your second brain?
Search works in two stages. First it checks an index that holds, per file, the title, a short summary from the first paragraph, the headings and the body text. If that finds nothing, it scans the full content of every markdown file. Results are capped at 20 per search.
The search matches words, not meaning. Claude makes up for that by trying more than one term: if “pricing change” finds nothing, it tries “price increase” or the customer’s name. You help by writing notes with a clear title and a first paragraph that says what the note is about. That summary is what Claude sees first in the search results.
INDEX_MAX_AGE_DAYS, 7 by default, sets how old a folder’s index can get before it is rebuilt on the next use. Writes through Claude update the index straight away. If you edit or add files outside Claude, ask it to run a reindex so search sees them.
What protects a second brain that Claude can write to?
Versioning. With VERSIONING_ENABLED=true, every write, append, move and delete becomes a git commit inside the vault. A write is then never an unrecoverable overwrite, and Claude can show the recent history of one file or the whole vault.
Two more safeguards protect your second brain. Deleting a file needs an explicit confirmation in the call. The .git folder can’t be reached through the tools at all, so the history itself is safe from the tools.
What does a week with a second brain look like?
On Monday you ask Claude to save the outcome of a meeting as a note. On Wednesday you ask it to append a follow-up to the same note. The next week you ask “what did we decide about the pricing change?” Claude searches, finds the note through its title and summary, reads it and answers, with the file path so you can open it yourself.
For meeting notes, the free meeting notes structurer skill turns a pasted transcript or bullet list into a structured note in your vault, with decisions, action items, open questions and links to related notes.
Common misconceptions
“It’s just markdown files in a folder.” The files are markdown, yes. The search index on top of them is what lets Claude find a note without you naming the file.
“Making changes by default is unsafe.” It is a different risk profile, and versioning covers it. Turn on VERSIONING_ENABLED and every change can be traced and undone.
“My notes need a fixed format.” No template is required. A clear title and a useful first paragraph make search work better, that’s all.
FAQ
Can I read the files without Claude?
Yes. They are markdown files in the vault/ folder of your install.
Does the vault sync between installations?
No. It belongs to one installation. Copy or back up the folder like any other data.
Can several people share one second brain?
Yes. Every seat with the Brain tool on the same license uses the same vault. Give each person the mode they need.
Wrapping up
A second brain only pays off when finding a note is faster than remembering it. Keep the vault on your own server, switch on versioning, write notes with a clear title, and let Claude do the filing. See what the Brain MCP server add-on includes, or read how to connect Claude to your notes.