FastMCP Server For Bidirectional Sync Between Personal And Team Obsidian Vaults
Let your coding agent trigger and manage bidirectional sync between your personal Obsidian vault and a shared team vault from one MCP connection.
Overview
vault-sync-mcp is a MCP server for the Build phase that bidirectionally syncs personal and team Obsidian vaults through FastMCP over stdio.
What is this MCP server?
- Bidirectional sync between two Obsidian vault roots via FastMCP stdio transport
- Requires PERSONAL_VAULT_PATH and TEAM_VAULT_PATH absolute paths in server config
- Ships as mcpb package v0.1.0 with pinned fileSha256 for reproducible installs
- stdio transport fits Claude Desktop, Claude Code, and other MCP stdio clients
- Server version 0.1.0
- 2 required environment variables: PERSONAL_VAULT_PATH, TEAM_VAULT_PATH
- Transport: stdio
What problem does it solve?
Splitting notes between a private Obsidian vault and a team vault means constant manual merging and missed updates when your agent only sees one folder.
Who is it for?
Solo builders or tiny teams using Obsidian plus Claude Code who need agent-callable sync between PERSONAL_VAULT_PATH and TEAM_VAULT_PATH.
Skip if: Teams on Notion-only stacks, cloud-only Obsidian Sync users who want zero local paths, or anyone needing conflict-free CRDT sync without Obsidian on disk.
What do I get? / Deliverables
After registration, your agent can drive two-way vault sync from configured paths so personal and team knowledge stay aligned without leaving the MCP workflow.
- Registered stdio MCP server with both vault paths configured
- Agent-callable bidirectional sync between personal and team vault roots
Recommended MCP Servers
Journey fit
Vault sync is agent-facing plumbing you wire up while assembling your knowledge and tooling stack, before you rely on shared notes in daily ship and operate work. Integrations is the canonical shelf for MCP servers that connect Claude Code or Cursor to local filesystem workflows rather than a hosted SaaS API.
How it compares
Local Obsidian vault MCP bridge, not a hosted note SaaS or a generic file-backup skill.
Common Questions / FAQ
Who is vault-sync-mcp for?
It is for Obsidian users who run MCP-capable agents and maintain separate personal and team vault directories on the same machine or mount.
When should I use vault-sync-mcp?
Use it when you are wiring agent tooling during build or operate and want programmatic bidirectional sync instead of exporting plugins or rsync scripts by hand.
How do I add vault-sync-mcp to my agent?
Install the mcpb release v0.1.0, set PERSONAL_VAULT_PATH and TEAM_VAULT_PATH to absolute vault roots, and add the stdio server entry to Claude Code, Cursor, or your MCP client config.