FastMCP server for bidirectional sync between personal and team Obsidian vaults

io.github.adelaidasofia由 GitHub 账号 adelaidasofia 发布v0.1.0更新于 Oct 24, 2026

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

发布方自己的服务:Fastio

概览

AI 生成的概览

本地 MCP 服务器,在个人 Obsidian 库与团队共享库之间双向同步笔记,支持状态查看、按规则推送/拉取和试运行预览。

可以做什么
  • 查看同步状态:列出待同步变更、过期文件和上次同步时间。
  • 把符合条件的文件从个人库推送到团队库。
  • 把团队库的变更拉取回个人库。
  • 检查某个文件是否在同步规则范围内。
  • 推送与拉取默认先试运行,预览后再执行。
适用场景
适合同时维护个人 Obsidian 库、并通过 Google Drive、Dropbox 等共享文件夹把部分笔记分享给团队的场景,希望助手报告待同步变更并按路径与 frontmatter 规则搬运文件。
运行要求
以 stdio 在本地运行,仅限桌面端,可作为插件或 Python 脚本安装。需要个人库与团队库的根路径,可在 config.yaml 中设置,或通过 VAULT_SYNC_PERSONAL、VAULT_SYNC_TEAM 环境变量提供(清单中声明的是 PERSONAL_VAULT_PATH 与 TEAM_VAULT_PATH)。传统安装方式需要 Python 及 fastmcp、python-frontmatter、pyyaml、xxhash。
安装前请注意
推送和拉取会写入两个库,请先试运行,并维护好 no_sync 列表与文件 frontmatter 中的 sync: false。冲突处理为较新文件胜出,冲突会被记录并跳过。插件首次加载时会向外部站点发送一次匿名安装信号,除非设置 MYCELIUM_NO_PING=1。

安装

在 SourceWeft 中

  1. 打开 控制台中的 FastMCP server for bidirectional sync between personal and team Obsidian vaults,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

vault-sync-mcp

[License] [GitHub stars] [Last commit] [Open issues] [PyPI version] [PyPI downloads] [Built by Mycelium AI]

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:

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

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

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

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

    bash
    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:

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.

来源:README.md,提交 f5169c6

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Fast 集成