Listed from the MCP registry; nobody on Odel publishes it.
FastMCP server for bidirectional sync between personal and team Obsidian vaults.
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Distributed as an MCP bundle (`https://github.com/adelaidasofia/vault-sync-mcp/releases/download/v0.1.0/vault-sync-mcp.mcpb`) — download it and import the bundle in your MCP client.
A FastMCP server for bidirectional sync between a personal Obsidian vault and a shared team vault. Designed for teams where one person (the vault owner) maintains the source of truth and shares selected content with collaborators via a shared folder (Google Drive, Dropbox, etc.).
| Tool | What it does |
|---|---|
vault_sync_status | Show pending changes, stale files, and last sync time |
vault_sync_push | Push eligible files from personal vault to team vault |
vault_sync_pull | Pull changes from team vault back to personal vault |
vault_scope_check | Check if a specific file is eligible for sync |
Both push and pull default to dry_run: true — you always preview before executing.
Open Claude Code, paste:
/plugin marketplace add adelaidasofia/vault-sync-mcp
/plugin install vault-sync-mcp@vault-sync-mcp
Then edit config.yaml to set your vault paths and sync rules:
personal_vault: ~/vault/
team_vault: ~/team-vault/
Restart Claude Code. Then ask:
"Show me vault sync status" "Push changes to team vault (dry run first)"
Clone:
git clone https://github.com/adelaidasofia/vault-sync-mcp.git
cd vault-sync-mcp
Edit config.yaml to set your vault paths and sync rules:
personal_vault: ~/vault/
team_vault: ~/team-vault/
Register with Claude Code:
claude mcp add vault-sync -s user -- sh /path/to/vault-sync-mcp/bin/uv-run python /path/to/vault-sync-mcp/server.py
Restart Claude Code. Then ask:
"Show me vault sync status" "Push changes to team vault (dry run first)"
Everything lives in config.yaml:
personal_vault: ~/vault/
team_vault: ~/team-vault/
no_sync:
- "Journal/"
- "Personal/"
sync_rules:
- path: "Team/"
direction: bidirectional
- path: "CRM/"
direction: personal_to_team
filter:
frontmatter_field: relationship
frontmatter_values: [client, team, advisor]
bidirectional — changes flow both wayspersonal_to_team — personal is source of truth, team gets updatesteam_to_personal — team is source of truth, personal gets updates (useful for shared docs)Add sync: false to any file's frontmatter to exclude it from all sync operations.
| Variable | Default | Description |
|---|---|---|
VAULT_SYNC_PERSONAL | from config.yaml | Personal vault root path |
VAULT_SYNC_TEAM | from config.yaml | Team vault root path |
os.walk(followlinks=True) instead of Path.rglob() to correctly handle macOS symlinks (Google Drive, iCloud shortcuts)[[folder/Note]] becomes [[Note]])Same author, same architecture pattern (FastMCP, draft+confirm on writes where applicable, vault auto-export, MIT):
This plugin sends a single anonymous install signal to myceliumai.co the first time it loads in a Claude Code session on a given machine.
What is sent:
slack-mcp)0.1.0)What is NOT sent:
Why: Helps the maintainer know which plugins people actually install, so attention goes to the ones that get used.
Opt out: Set the environment variable MYCELIUM_NO_PING=1 before launching Claude Code. The hook will skip the network call entirely. Already-pinged installs leave a sentinel at ~/.mycelium/onboarded-<plugin> — delete it if you want to reset state.
MIT
Built by Mycelium AI. Full install or team version at diazroa.com.