Back to Browse

Vault Sync MCP Server

SecurityUse Caution4.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

FastMCP server for bidirectional sync between personal and team Obsidian vaults.

About

FastMCP server for bidirectional sync between personal and team Obsidian vaults.

Security Report

4.2
Use Caution4.2High Risk

This is a well-structured FastMCP server for Obsidian vault synchronization with appropriate authentication through file-based configuration and proper authorization controls. The code demonstrates good security practices including path validation, frontmatter-based blocking, and dry-run defaults. Minor code quality issues around broad exception handling and telemetry transparency do not substantially impact security posture. Supply chain analysis found 5 known vulnerabilities in dependencies (1 critical, 3 high severity).

4 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Absolute path to your personal Obsidian vault rootOptional

Environment variable: PERSONAL_VAULT_PATH

Absolute path to your team Obsidian vault rootOptional

Environment variable: TEAM_VAULT_PATH

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-adelaidasofia-vault-sync-mcp": {
      "env": {
        "TEAM_VAULT_PATH": "your-team-vault-path-here",
        "PERSONAL_VAULT_PATH": "your-personal-vault-path-here"
      },
      "args": [
        "-y",
        "github:adelaidasofia/vault-sync-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

vault-sync-mcp

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.).

Tools

ToolWhat it does
vault_sync_statusShow pending changes, stale files, and last sync time
vault_sync_pushPush eligible files from personal vault to team vault
vault_sync_pullPull changes from team vault back to personal vault
vault_scope_checkCheck if a specific file is eligible for sync

Both push and pull default to dry_run: true — you always preview before executing.

Install

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)"

pip install fastmcp python-frontmatter pyyaml xxhash
  1. Clone:

    git clone https://github.com/adelaidasofia/vault-sync-mcp.git
    cd vault-sync-mcp
    
  2. Edit config.yaml to set your vault paths and sync rules:

    personal_vault: ~/vault/
    team_vault: ~/team-vault/
    
  3. Register with Claude Code:

    claude mcp add vault-sync -s user -- python3 /path/to/vault-sync-mcp/server.py
    
  4. Restart Claude Code. Then ask:

    "Show me vault sync status" "Push changes to team vault (dry run first)"

Configuration

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]

Sync rule directions

  • bidirectional — changes flow both ways
  • personal_to_team — personal is source of truth, team gets updates
  • team_to_personal — team is source of truth, personal gets updates (useful for shared docs)

Blocking sync on a file

Add sync: false to any file's frontmatter to exclude it from all sync operations.

Environment variables

VariableDefaultDescription
VAULT_SYNC_PERSONALfrom config.yamlPersonal vault root path
VAULT_SYNC_TEAMfrom config.yamlTeam vault root path

Notes

  • Uses os.walk(followlinks=True) instead of Path.rglob() to correctly handle macOS symlinks (Google Drive, iCloud shortcuts)
  • Wikilinks are automatically rewritten to bare filenames during push ([[folder/Note]] becomes [[Note]])
  • Content hashing via xxhash for fast change detection
  • Conflict resolution: newer file wins; conflicts are logged and skipped

Related MCPs

Same author, same architecture pattern (FastMCP, draft+confirm on writes where applicable, vault auto-export, MIT):

Telemetry

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:

  • Plugin name (e.g. slack-mcp)
  • Plugin version (e.g. 0.1.0)

What is NOT sent:

  • No user identifiers, names, emails, tokens, or API keys
  • No file paths, message content, or anything from your work
  • No IP address is stored after dedup processing

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.

License

MIT


Built by Mycelium AI. Full install or team version at diazroa.com.

Reviews

No reviews yet

Be the first to review this server!