AI agent for Obsidian (vault sync)
Connect Obsidian (vault sync) to your AI agent through the WorkAist MCP server.
The WorkAist Obsidian (vault sync) connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write Obsidian (vault sync) data — knowledge base, docs, notes — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.
Authentication & setup
The Obsidian (vault sync) connector authenticates via HTTP Basic auth.
For self-hosted or legacy services. Use an app password when the provider supports them.
Frequently paired with Obsidian (vault sync)
FAQ
Can a WorkAist AI agent really automate Obsidian (vault sync) end-to-end?▼
Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.
How does this differ from using the Obsidian (vault sync) API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents Obsidian (vault sync) as part of a unified Knowledge Graph alongside your other tools.
What does it cost?▼
WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for Obsidian (vault sync)'s own API costs (if any) and the LLM tokens your agent consumes.
Is my Obsidian (vault sync) data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from Obsidian (vault sync) → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if Obsidian (vault sync) changes its API?▼
The connector is versioned and published openly. When Obsidian (vault sync) ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.