This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
A lightweight, self-hosted MCP server that turns a plain folder of markdown into memory your AI agent can read and write. One 24 MB container, no database, no embeddings, no lock-in. Your notes stay flat files you own in git, Obsidian, or any editor. 15 MCP tools, its own OAuth, conflict-safe writes. MIT.
Hi Product Hunt! I'm Tomáš, the maker of vellum.
I kept giving my AI assistant "memory" and kept ending up with the same problem: the memory lived in someone else's database, as embeddings I couldn't read, in a cloud I didn't control. So I built the opposite.
vellum is a tiny self-hosted MCP server over a plain folder of markdown. Your agent reads and writes notes straight into the folder, and the folder stays flat files you own: git, Obsidian, grep, any editor. No database, no embeddings, no vendor lock-in. One 24 MB container, `docker compose up -d`, and you're done.
It's fully open source (MIT). I'd love your feedback, especially on the MCP tool surface (15 tools today) and where you'd want it to go next.
Per-agent path scoping — token → directory mapping, so one vault can safely serve multiple agents. An assistant gets loose on my work notes while my personal journal stays completely off limits. Same vault, different scope.
A desktop app — so you don't have to touch Docker at all. Same Go binary under the hood, just a one-click window into your vault.
An observability layer — it captures my Claude Code / Claude Desktop conversations, then a deterministic curator step files them into markdown for later analysis. Memory that writes itself, still as flat files you own.
All of it keeps the same rule: no database, no embeddings, no lock-in, one small Go binary.
finally something that respects my markdown obsession, spun it up in docker and my agent was reading my obsidian vault in under a minute. love that the files stay flat
The conflict-safe writes sound great since I have run into merge issues before with sync tools. One thing that would help me a lot is a built-in way to tag or scope which folders a given agent can touch, so my personal journal stays off limits when I let an assistant loose on work notes. Maybe something like per-call path prefixes or a config map that maps agent tokens to allowed directories.
About Vellum on Product Hunt
“Self-hosted MCP server over a folder of markdown”
Vellum was submitted on Product Hunt and earned 15 upvotes and 6 comments, placing #44 on the daily leaderboard. A lightweight, self-hosted MCP server that turns a plain folder of markdown into memory your AI agent can read and write. One 24 MB container, no database, no embeddings, no lock-in. Your notes stay flat files you own in git, Obsidian, or any editor. 15 MCP tools, its own OAuth, conflict-safe writes. MIT.
Vellum was featured in Open Source (68.6k followers), Developer Tools (516.2k followers), Artificial Intelligence (474.1k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 223.9k products, making this a competitive space to launch in.
Who hunted Vellum?
Vellum was hunted by Tomáš Grasl. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Vellum stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Tomáš Grasl