iCloud-synced vaults are the common Obsidian setup on a Mac and the least convenient to reach: a container path with tildes in it that has to be escaped correctly in JSON. This exists to make that work, and passing several paths means a personal and a work vault can share one server entry. The platform caveat is stated rather than assumed — macOS is the tested surface.
An MCP server for Obsidian vaults that live in iCloud Drive, where the path is long and awkward enough that most tools trip over it. Vault paths are passed as launch arguments, and more than one can be given, so several vaults are reachable from a single entry.
- Vaults inside the iCloud Obsidian container reachable by an assistant
- Multiple vaults from one server entry — each path is another launch argument
- A published package, so the client config is `npx -y obsidian-mcp` plus the paths, with no build step
Node, and the absolute path to each vault under `Library/Mobile Documents/iCloud~md~obsidian/Documents/` — the README shows the escaping the config needs. Production use is `npx -y obsidian-mcp` with the paths as arguments; development runs `node build/index.js` against a local checkout, inspectable with the MCP inspector. The package is `obsidian-mcp` (1.0.0 in package.json). It is fully tested on macOS only — the README asks Windows and Linux users to report whether it works.