How I use AI
I use AI mostly to understand. To have a mechanism explained, to look at a problem from an angle I do not know yet, to borrow knowledge I do not have and check it. It knows things I don't; I ask, I read, I verify.
I do not use it to think in my place. I stay the one who reasons and decides; the assistant helps. A familiar, not a replacement.
These servers exist for that: an assistant is only as useful as what it knows of my context. MCP (Model Context Protocol) lets me hand it my notes, my kitchen or my accounts, with tools I wrote and limits I chose.
The keeper of notes
ObsidianGraph.Mcp. My notes already link to each other, so instead of cutting them into chunks and searching them blind, the server lets Claude and Gemini walk the graph of links: map a topic, read a summary, then one section, then the whole note only if needed. It saves tokens and gives better answers. Both assistants share it as one memory and write notes themselves, following one template.
- Graph in memory as adjacency lists, notes parsed with source-generated regular expressions, re-indexed when a file changes.
- Typed relations written in the note itself, such as uses:: [[link]].
- OAuth 2.1 only.
The keeper of the larder
Cuisine.Mcp. I send a photo of the fridge; the stock is updated, shelf by shelf. Shopping and dinner ideas come from what is there, what expires soon and what I usually eat, and recipes come from my own cookbook. The view appears inside the chat, through MCP Apps.
- .NET 10 with no NuGet package: I wrote the protocol by hand.
- One JSON file written atomically, plus an append-only history.
- Names compared without accents or ligatures; units never converted silently.
The keeper of the ledger
CompteRendu.Mcp. Once a month it tells me where the money went, from the bank's export and from supermarket receipts read line by line.
- Data in CSV files, readable without the tool; the server sees one folder and nothing else.
- A receipt is accepted only if its lines add up to the total; duplicates are caught by the receipt's own code.
- xUnit tests on real receipts.
What they share
C# and .NET, Docker on my Synology NAS, authentication on every call. They are reachable only by my own assistants. None of them is meant to become a public product: they are tools shaped around one person's habits, and that is the point.