# AI to organize notes: the ones that can move a file, and what a team should let them touch

> The best AI to organize notes is one that can move, rename and merge them safely. Notion Agent, Claude over MCP, and what changes when a team shares the notes.

Source: https://baalda.com/blog/ai-to-organize-notes
Site: Baalda, https://baalda.com
Published: 2026-10-25

**Short answer.** The best AI to organize notes is one that can move, rename and merge them, not only summarize them. In Notion that is Notion Agent. On markdown files it is Claude or another assistant over MCP. For notes a team shares, Baalda checks every move against the asking person's permissions and keeps each note's id and history.

The best AI to organize notes is the one that can actually move them: rename a file, file it into a folder, merge two duplicates, without breaking links or overwriting someone. Inside Notion that is Notion Agent, on markdown files it is Claude or another assistant connected over MCP, and for notes a whole team shares it is an assistant working through a server that checks, on every move, whether the person asking is allowed to make it.

Most round-ups of AI note apps grade the wrong half. They test summaries, chat with your notes and auto-tagging, which are all reads. Organizing is a write. An assistant that reads beautifully and cannot move a file will hand you a tidy plan and leave the mess exactly where it was.

## What is the best AI to organize notes?

It depends on where the notes already live, because the assistant has to be able to write there.

| Your notes live in | AI that can organize them | What it can move |
|---|---|---|
| Notion | Notion Agent | Pages and databases in your workspace, with your permissions |
| Obsidian, one person | A community plugin, or Claude over a filesystem MCP server | Markdown files in the folders you allow |
| A folder of markdown on your disk | Claude, or any MCP client, with the reference filesystem server | Files and directories on an allowlist |
| Markdown a team edits together | An MCP client connected to Baalda | Notes and folders, checked against each person's access |

Notion's own help page says Notion Agent can "help you create and edit pages and databases using context from your workspace and connected apps", and that it "has the same permissions you do. If you can't view or edit specific content, your agent can't either." If your notes are already in Notion, that is the shortest path, and nothing below beats it for a single workspace. The same page lists what it cannot do, including sharing pages or changing page permission levels, and creating templates or page layouts.

The Obsidian app, as of October 2026, ships no assistant of its own. AI arrives through community plugins such as Smart Connections and Copilot, or from outside the app entirely, which is where MCP comes in.

## What does organizing actually ask the AI to do?

Five operations, and only the first is a read.

1. **Survey.** List every note and folder and read enough of each to know what it is.
2. **File.** Move a note into the folder it belongs in.
3. **Rename.** Give a note or a folder a name a person would search for.
4. **Merge.** Fold two near-duplicate notes into one and remove the spare.
5. **Archive.** Move what is finished out of the way without deleting it.

Each of the last four can go wrong in a way a summary never can. A move can break every link that pointed at the old path. A merge rewrites a note somebody else was editing a minute ago. A delete removes the only copy. That is why the useful question about an AI organizer is not how clever it is but what it is allowed to change, and what stops a bad change from sticking.

## Can Claude organize the notes on my own computer?

Yes. The reference filesystem MCP server from the Model Context Protocol project gives an assistant thirteen tools over directories you name, including `move_file`, `create_directory`, `edit_file` and `write_file`. Its README says the server only touches directories on its allowlist, and that `move_file` fails if the destination already exists, which is the right default for a reorganization. It also marks `move_file`, `edit_file` and `write_file` with `destructiveHint: true`, a signal a client can use to ask before running them.

For one person with a folder of markdown, that is a complete setup, and it is free. Two limits are worth knowing before you point it at a real vault.

- **It moves files, not notes.** The server knows paths. If your notes link to each other by filename, a renamed file can leave links pointing at a name that no longer exists. Obsidian updates internal links when you rename a file inside Obsidian (or prompts you to, depending on a setting), but a program moving files on disk is not Obsidian renaming them.
- **It has no idea who is asking.** The allowlist belongs to the server process, so anyone using that process gets the same reach. On your own laptop that is you. On a shared folder it is everyone, which is the problem [an MCP server for team notes](/blog/mcp-server-team-notes) has to solve.

## What changes when an AI organizes a team's notes?

The notes stop being yours. A tidy-up you would happily run on your own vault now moves a teammate's meeting notes, renames the folder the sales team links to, and deletes what looked like a duplicate but was someone's draft. The assistant needs the same limits a person would have, and it needs them on every call, not once in a config file.

This is the part Baalda is built for. Baalda is a team second brain: plain markdown files on your own disk, real-time multi-user editing, per-file permissions, open source under Apache-2.0 and self-hostable. It serves MCP at `POST /api/mcp` on the team's own server, and each connection carries a token minted by one person, so the assistant acts as that person and nobody else.

The organizing tools are the ones the job needs, and each is gated by the caller's access:

- `list_folders` and `list_notes` return only what the caller can reach, and `list_notes` reports the caller's permission on each note, so the survey step never sees a note it could not open in the app.
- `move_note` renames, moves or retitles a note. Its tool description is specific: "The note keeps its docId and its full history, so links and edits survive."
- `move_folder` moves a whole folder, rewriting "every descendant path" while every docId is preserved. Without edit access it is refused with "You do not have edit access to move this folder".
- `edit_note` makes targeted edits by exact anchor. If an anchor is missing or matches more than once, the whole call is refused "with nothing written".
- `delete_note` is a soft delete, into a Trash the server keeps for 30 days.

The full list, with every input, is on the [MCP tools reference](/docs/mcp-tools).

## What does a safe reorganization look like as tool calls?

A merge is where most of the damage happens, so it is the one worth showing. The assistant reads both notes, keeps the revision it read, and writes with it:

```json
{ "name": "read_note", "arguments": { "docId": "n_8f2c" } }

{ "name": "update_note", "arguments": {
    "docId": "n_8f2c",
    "content": "# Pricing decisions\n\n...merged text...",
    "expectedRevision": "r_41"
} }

{ "name": "move_note", "arguments": {
    "docId": "n_3a91",
    "relPath": "Archive/pricing-old.md"
} }
```

If a teammate edited the pricing note between the read and the write, `expectedRevision` no longer matches and the write is refused with a conflict instead of quietly replacing their paragraph. The assistant reads again and retries. The spare copy is archived with `move_note` rather than deleted, so it keeps its id and history and anyone looking for it can still find it. The ids above are illustrative; the shapes are the real ones. The `Archive` folder has to exist first, which `create_folder` takes care of.

Baalda also labels every tool with the MCP annotations: reads are `readOnlyHint`, `update_note` and the deletes are `destructiveHint`, moves are marked idempotent. The spec says clients "SHOULD" ask for confirmation on sensitive operations, and also that annotations "MUST" be treated as untrusted unless they come from a trusted server, so what your client does with them is up to your client. Worth checking before a large run, along with the rest of [what makes MCP risky](/blog/is-mcp-safe).

## How do I ask an assistant to reorganize shared notes?

In three passes, with a person reading between them.

1. **Plan in a note, not in the chat.** Ask the assistant to survey the vault and write the proposed structure into a new note: which folders, what moves where, which pairs it thinks are duplicates. The plan is then something the team can read and edit, not a reply that scrolls away.
2. **Move in small batches.** One folder at a time. Moves are the cheap, reversible part, because the note keeps its id and history.
3. **Merge and archive last.** These rewrite content, so they go after everyone has seen the plan, and they archive rather than delete.

Because the assistant writes into the same files the team has open, everyone sees the moves as they happen, and a move that was a mistake is one more move to undo.

## Where Baalda does not help

It will not decide your structure. Whether projects or clients or quarters make the better top level is a judgment the assistant can propose and a team has to make, and a bad taxonomy filed perfectly is still a bad taxonomy.

It does not organize in the background. There is no setting that files new notes on its own; an assistant does the work when someone asks it to, through the tools above.

Renames are not the same as moves. A move keeps links because the note keeps its id. A rename that changes a filename other notes link to by name is worth checking afterwards in the note's backlinks.

And if your notes are in Notion, or you are one person with one Obsidian vault, you probably do not need it. Notion Agent or a plugin will organize a personal workspace with less setup, and the [Baalda and Notion comparison](/compare/notion) is honest about when Notion is the better home. Baalda earns its place when several people, and their assistants, are moving the same notes.

## FAQ

### Can AI organize my notes for me?

Yes, if it can write where the notes live. Notion Agent can create and edit pages and databases in Notion with your permissions. For markdown files, Claude or another MCP client can move, rename and edit them through an MCP server such as the reference filesystem server or Baalda. An assistant that can only read your notes can suggest a structure but cannot apply it.

### Does Obsidian have a built-in AI to organize notes?

Not as of October 2026. The Obsidian app ships no assistant of its own; AI comes from community plugins such as Smart Connections and Copilot, or from an outside assistant connected to the vault folder over MCP. Obsidian updates internal links when you rename a file inside the app, but a program moving files on disk bypasses that.

### Will moving notes with AI break my links?

It depends on the tool. A server that only knows file paths can leave links pointing at a name that no longer exists. In Baalda, move_note and move_folder keep each note's id and full history, so links and edits survive a move. A rename that changes a filename other notes link to by name is still worth checking in the backlinks afterwards.

### How do I stop an AI from reorganizing notes it should not touch?

Give it a connection that acts as one person and is checked on every call. In Baalda each MCP token belongs to the person who minted it, list_notes only returns notes that person can reach, and a move without edit access is refused. A folder allowlist on a filesystem server limits where it can go but applies the same reach to everyone using that server.