Three tools that each do one thing well. Together they do something that none of the three, alone, can do.

Worth looking at what each does before seeing what happens when they work together.

Obsidian: the editor that doesn't lock you in

Obsidian is a text editor for markdown files. The files live on your disk, in regular folders. They open with any text editor, even without Obsidian. The "vault" is just a folder that Obsidian indexes and displays with its features — wikilinks (the double square brackets [[ ]] that link one note to another like Wikipedia pages), relationship graph, plugins, formatted preview — but the content is and remains plain text.

Obsidian isn't a cloud service. It's software that runs on your device and reads files that are yours, in a standard format. If Obsidian disappeared tomorrow, your files would stay.

Timo: the bridge between the vault and the AI

Timo is a server: it indexes the vault, exposes semantic and full-text search through the MCP protocol, allows AIs to read and write notes in a structured way.

When an AI asks "find all notes about X", Timo replies with the relevant passages. When the AI wants to annotate something new, Timo writes it into the vault as a new markdown file.

Timo isn't an editor and isn't an AI. It speaks a standard protocol (MCP), not a proprietary one. Any compatible client can connect.

The AI: the brain, separate

The AI in this scheme isn't an integrated app. It's a separate service — Claude, ChatGPT, a local model, a custom agent — that connects via MCP to the vault's memory.

The AI does what AIs do well: understand language, reason, synthesize, rephrase. It does so having access, through Timo, to the content you've accumulated in Obsidian.

What happens together

Concrete example. You're working on a project that lasts months. In your Obsidian notes, month after month, you've put:

  • the project's requirements list,
  • notes from client meetings,
  • architectural decisions with their rationale,
  • drafts of technical documents,
  • errors encountered and how you solved them.

All in markdown, well linked with wikilinks.

One morning, after weeks of not touching the project, you need to pick up the thread. You open a chat with an AI. You ask:

"Summarize where we are on project X. Which architectural decisions have we made, which are still open, which errors have we encountered and how did we tackle them."

The AI through Timo searches the vault. Finds the relevant notes. Reads them. Replies citing the files. You get in five minutes what would have taken you an hour of manual rereading.

It's not magic. It's that each of the three components did its part:

  • Obsidian had preserved the content in a readable format,
  • Timo had indexed it and made it searchable,
  • The AI read and reasoned on top.

A specific detail worth highlighting: wikilinks in Obsidian create a graph of relationships between notes.

For Timo, this graph is readable. When the AI follows a note, it can also follow the links that note contains, and from there to other connected notes. The vault's structure stops being a simple collection of disconnected documents and becomes a navigable network.

For the user, the graph helps their own visual memory. For the AI, the graph is an exploration path. Same object, two compatible uses.

Unix philosophy, applied

The Obsidian + Timo + AI scheme is a modern rereading of an old idea: each tool does one thing, does it well, and combines with the others through simple interfaces.

The editor isn't a cloud app. The memory server isn't an AI. The AI isn't an editor. Each has clear boundaries. Replace one (change AI, change markdown editor) and the rest keeps working.

It's a powerful combination precisely because it isn't integrated into a single product. It's a pipeline, not a platform.

Try Timo free for 15 days — timoai.xyz. No credit card required.