AI agent for Obsidian (vault sync)

Connect Obsidian (vault sync) to your AI agent through the WorkAist MCP server.

/ agents/marketplace

Marketplace

Pre-built connector templates · install with one click.

Connector
Obsidian (vault sync)
Production-grade knowledge base MCP server. AGPL-3.0, self-hosted.
v1.3.3knowledge basebasic
  1. 1Install in one click

    Pick Obsidian (vault sync) from the marketplace. WorkAist handles HTTP Basic auth and stores the credentials encrypted — no JSON keys to paste.

  2. 2Tools auto-generated

    Obsidian (vault sync) exposes 6 MCP tools to every agent in your workspace: search_articles, list_articles, create_article, get_views, and more. Each tool is a typed function, not a brittle script.

  3. 3Data flows to your graph

    Historical knowledge base records sync to your private knowledge graph. Agents query relationships across all connected sources, not just Obsidian (vault sync) in isolation.

  4. 4Your agents take action

    Your AI agent picks the right tool, runs it under your access policies, and answers in plain language — with a full audit trail of every Obsidian (vault sync) call.

In 60 seconds

Obsidian (vault sync) is knowledge base software you can connect to WorkAist in minutes. Through the open MCP standard, your AI agents classify tickets, draft grounded answers and escalate the genuinely hard cases — autonomously, under explicit permissions, with no manual hand-offs. Obsidian (vault sync) authenticates via username and password, and because WorkAist is self-hosted under AGPL-3.0, your data never leaves your own infrastructure.

Authentication & setup

The Obsidian (vault sync) connector authenticates via HTTP Basic auth.

Username + password / app password

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.

Licensed under AGPL-3.0 · Self-hosted, your data stays yours.