Why use Obsidian as a mirror instead of the primary store
Obsidian's strength is local-first editing, a beautiful editor, and the plugin ecosystem. Its weak point for the AI workflow is the MCP server: there is no built-in one, and the community plugins require setup per machine, with no shared state between devices. Hjarni inverts that: the knowledge lives once, in the cloud, with a remote MCP server every AI client can read from.
Treating Obsidian as a one-way mirror gets you both: cloud-hosted knowledge that AI assistants reach over MCP, and a local Markdown vault you can read, search, and graph offline. If you stop using Hjarni, you still have the vault. If you stop using Obsidian, you still have the notes in Hjarni.
If you would rather move an existing vault into Hjarni instead, the regular import flow at /import/new accepts a ZIP of your Obsidian vault with folders, frontmatter, wiki-links, and attachments intact. Mirror and import solve different problems — mirror for ongoing read-only sync, import for a one-time move.