# Build a second brain in Obsidian that more than Obsidian can read

> How to build a second brain in Obsidian: folders, properties, links, daily notes and plugins, set up so an AI or a teammate can read the vault too.

Source: https://baalda.com/blog/obsidian-second-brain
Site: Baalda, https://baalda.com
Published: 2026-10-14

**Short answer.** Make one vault with an inbox and Projects, Areas, Resources and Archive folders. Turn on Daily notes and Templates, give each note a few properties, and link with wikilinks. Keep the answers in the files rather than in plugin queries, so an AI assistant or a teammate reading the folder sees what you see.

To build a second brain in Obsidian, make one vault, give it four folders and an inbox, put properties at the top of each note, link notes with wikilinks, and let daily notes catch everything else. That takes an afternoon. The decision that matters comes later, when you choose whether the answers live in the files or only in what Obsidian renders on screen.

Most guides skip that decision because they assume one reader: you, inside Obsidian. The moment anything else reads the folder (an AI assistant, a script, a teammate in another app), the difference shows. A dashboard built from a plugin query is a list on your screen and a block of code in the file. This guide builds the vault so the file is the answer, which is also what lets the same folder open in Baalda, the app this site is for, and be read by an AI over MCP without Obsidian running.

## What is a second brain in Obsidian, in practice?

Obsidian's help defines a vault as a folder on your local file system where Obsidian stores your notes. That sentence is the whole architecture. Every note is a `.md` file, every attachment is a file next to it, and Obsidian's own settings sit in a hidden `.obsidian` folder inside. There is no database to export from.

So a second brain in Obsidian is a folder of markdown with conventions on top: where things go, what each note says about itself, and how notes point at each other. The app adds search, backlinks, a graph and plugins. The conventions are yours, and they are the part that outlives any particular app. If you want the method behind the conventions, [how to build a second brain](/blog/how-to-build-a-second-brain) walks through Tiago Forte's four steps and where they stop.

## How do you set up the vault, step by step?

1. **Create one vault.** One. A second vault for work is fine later, but notes that cannot link to each other cannot become a second brain.
2. **Add an inbox and four folders.** `00 Inbox` for anything you have not sorted, then Projects, Areas, Resources and Archive, the PARA layout. Folders are for where a note lives now, not what it is about. Topics go in links and properties.
3. **Turn on Daily notes and Templates.** Both are core plugins. Daily notes opens today's note or creates it, and you can point it at a template so every day starts with the same headings. Most capture lands here first.
4. **Write a properties template.** Properties are stored as YAML at the top of the file, between two lines of `---`. Decide on four or five you will actually fill in, and put them in a template.
5. **Link while you write.** Type `[[` and pick a note. Obsidian uses wikilinks by default and can update every link when you rename a file, so link freely and rename later.
6. **Review the inbox weekly.** Move each note to a folder, add a link or two, and delete what no longer matters.

A note made from that template looks like this, and every line of it is readable by anything that can open a text file:

```markdown
---
type: decision
status: accepted
project: "[[Billing rewrite]]"
date: 2026-10-14
---

# Move invoices to the new ledger

We are moving invoices first because they have the fewest writers.
Rejected: migrating everything at once (see [[Ledger spike notes]]).
```

## Which plugins does an Obsidian second brain need?

Fewer than the guides suggest. The core set (Daily notes, Templates, Backlinks, Outgoing links, Graph view, and Bases if you want table views) covers the jobs most plugin lists are trying to fill.

The question to ask of any plugin is not how useful it is but where its output lives. That splits plugins into two kinds:

| Plugin does this | Where the result lives | Readable outside Obsidian? |
|---|---|---|
| Adds or edits text (templates, daily notes, link updates on rename) | In the `.md` file | Yes |
| Stores data as properties | In the YAML at the top of the file | Yes |
| Renders a view from a query (Dataview, embedded queries) | Only on screen, at render time | No, the file holds the query |
| Draws a canvas or board | In a separate JSON file | Partly, as raw data |

Bases is a useful middle case. Obsidian's help says "All the data in Obsidian Bases is stored in your local Markdown files and their properties", so the data survives anywhere. The table view itself is described in a `.base` file or a code block, and only Obsidian draws it.

## Why does it matter where the answers live?

Here is a typical project dashboard built with the Dataview community plugin:

```dataview
table status, date
from "Projects"
where type = "decision"
sort date desc
```

In Obsidian that renders as a tidy table of every decision. In the file, it is those five lines. An AI assistant that reads the vault through the filesystem or an MCP server reads the five lines, not the table. A teammate who opens the folder in any other editor sees the same. Your second brain answers the question "what have we decided" only while one particular app is open on one particular machine.

The fix is not to drop plugins. It is to keep anything another reader needs in a form that is already the answer:

- **Facts go in properties**, which are plain YAML. A query over them can be rebuilt in any tool.
- **Relationships go in wikilinks**, written into the text, not inferred by a plugin.
- **Indexes are written down.** If a list of decisions matters, keep a `Decisions.md` note with a line per decision and a link. Use the Dataview table as a check that the index is complete, not as the index.
- **Context for an assistant goes in a note.** A short `README.md` at the vault root that says what each folder is for is what an assistant should read first, and it costs five minutes.

## What changes when an AI or a second person reads the vault?

Up to here, Obsidian is the right tool and you may never need another one. It is free for personal and commercial use, it is fast, and the plugin ecosystem has no equal. The second reader is where it stops being enough on its own.

For an AI, Obsidian has no server, so anything that reads your vault is a process running next to your copy of the folder. The options are covered in [MCP servers for Obsidian](/blog/mcp-server-for-obsidian); the popular ones go through a community plugin and need Obsidian open on that machine. A cloud assistant, or one running on a colleague's laptop, has nothing to connect to.

For a second person, Obsidian Sync can share a vault, but every collaborator gets the owner's permissions and there is no live co-editing yet. [Obsidian for teams](/blog/obsidian-for-teams) sets out the costs and limits.

This is the gap Baalda fills, and it fills it at the file layer this guide has been building. Baalda opens a folder of plain `.md` files, so moving an Obsidian vault is a copy: folders, properties and `[[wikilinks]]` come across as they are, and Baalda resolves the same wikilinks into backlinks and indexes the same frontmatter. On top of the folder it adds three things:

- **An MCP endpoint that does not need Obsidian running.** The vault is reachable at your server URL plus `/api/mcp`, with a bearer token per client. An assistant gets tools such as `search_notes`, `read_note` and `edit_note`, and a write can carry the note's revision so it is refused if someone changed the note in between. Setup for Claude, Cursor and others is in the [MCP setup guide](/docs/mcp-setup).
- **Permissions per file.** Each person gets Can edit, Can view or No access on the vault, a folder or one note, and an assistant connected with your token reaches only what you can.
- **Live editing.** Two people, or a person and an assistant, in the same note at once, merged as they type through a CRDT rather than file by file.

This is also why the file-first rule above pays off. A vault whose indexes are written down is equally useful to you in Obsidian, to a colleague in Baalda, and to an assistant reading over MCP. A vault built on query plugins is useful only in the first of those.

## Where does Baalda not help?

If the second brain is only ever yours, you do not need it. Obsidian on one machine, or with Sync across your own devices, is the better setup.

Baalda has no plugin system, so Dataview queries and Bases views do not render in it, and a Canvas file is indexed as plain text rather than drawn. It is desktop only, on macOS, Windows and Linux, with no mobile app yet. If your vault depends on plugins or you capture mostly from a phone, keep Obsidian as the place you write and decide later whether the folder needs a second reader.

## Is Obsidian the best app for a second brain?

For one person who wants plain files, links and an unmatched plugin library, yes, and that covers most people searching for this. It is the wrong place to stop if the second brain is supposed to be read by people other than you, or by an assistant you do not run on your own laptop. Build it in Obsidian either way. If you keep the answers in the files, the folder works wherever it ends up.

## FAQ

### How do I create a second brain in Obsidian?

Create one vault, add an inbox and the four PARA folders, and switch on the Daily notes and Templates core plugins. Write a template with four or five properties you will actually fill in, link notes with wikilinks as you write, and empty the inbox once a week.

### Is Obsidian the best second brain?

For one person, it is the strongest choice: plain markdown files on your disk, free for personal and commercial use, and the largest plugin library. It stops being enough when someone else needs the vault, because shared vaults give every collaborator the owner's permissions and an AI needs a process running beside your copy of the folder to reach it.

### Which Obsidian plugins does a second brain need?

Mostly core ones: Daily notes, Templates, Backlinks, Graph view, and Bases for table views. Before adding a community plugin, check where its output lives. Plugins that write into the file are portable. Query plugins such as Dataview render results only inside Obsidian, so the file holds the query and not the answer.

### Can an AI read my Obsidian second brain?

Yes. A local agent can read the folder directly, and MCP servers for Obsidian expose it to assistants, most of them through a community plugin that needs Obsidian open. Baalda opens the same folder of markdown and serves it over its own MCP endpoint, scoped to each person's permissions, without Obsidian running.