Import that ends in Markdown
Drop in a web page, a PDF or a long email. The agent converts it to Markdown, pulls out a title and files it in the vault instead of an inbox you never open again.
Mino is an Obsidian alternative with the AI built into the app, not a panel added later. It runs on your server, works inside your Markdown vault, and does the filing you keep postponing: imports, tags, links, summaries and retrieval.
Capture got solved years ago. A share sheet, a web clipper, a voice memo: getting something into the notes app takes a second and works. What nobody solved is the day after, when the tenth unsorted capture lands next to the other nine.
A folder tree asks you to make a classification decision at the worst possible moment, before you know what the note is for. A search box helps only if you remember the word you used six months ago. So the notes pile up, and the pile slowly becomes a graveyard.
Mino inverts the order: capture first, decide later. The agent does the filing, and you correct it when it gets something wrong.
Nothing happens off your server. Three operations run on your files:
Drop in a web page, a PDF or a long email. The agent converts it to Markdown, pulls out a title and files it in the vault instead of an inbox you never open again.
New material is matched against what you already have: tags get reused instead of reinvented, related notes get linked, and the folder tree stays shallow on purpose.
Full-text search works with no setup; embeddings make it semantic once you configure a provider. Ask a question and the answer arrives with the notes it came from.
A chat panel bolted onto an editor only knows the note you have open. Mino exposes the vault itself over the same HTTP API the UI uses, plus an MCP bridge. Point Cursor at it and the agent there can search your notes; point a cron job at it and a nightly run can file whatever landed in the inbox folder.
Because the notes are plain Markdown, the agent is never the only way in. grep, sed, a Git remote, or an editor you already like — all of it still works on the same files.
One email at launch, nothing else. If you would rather not wait, the repository and the docs are public today.
You bring the key. The agent stays disabled until you configure a provider, model and API key on your server, so you choose which model sees your notes and you pay that provider directly.
Yes, including an Obsidian vault. Markdown with YAML front matter is the native format, so it drops in as-is, folders included. The SQLite index is rebuilt from the files, not the other way round.
Yes. Every note operation is exposed over the same HTTP API the UI uses, with an X-Mino-Key header, and an MCP bridge exposes it to clients like Cursor or Claude. An outside agent can search, read, create and move notes in the vault.
It proposes structure first: where a note should file, which notes it should link. Every action is reported in the conversation rather than applied silently. The vault stays editable by hand, because it is only files.