LabscoMCP early access ↗
YanceyOfficialMCP SERVER

Obsidian iCloud MCP

Connect Obsidian vaults stored in iCloud Drive to an assistant — pass the vault paths on the command line and it reads them.

by YanceyOfficial ↗Note-Taking & Personal Knowledge BasesCommunity

LABSCO SUMMARY

Built for one specific annoyance.

iCloud-synced vaults are the common Obsidian setup on a Mac and the least convenient to reach: a long container path, with a space and tildes in it, buried under your Library folder. 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.

What it is

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.

What you get

  • Vaults inside the iCloud Obsidian container reachable by an assistant
  • Multiple vaults from one server entry — each path is another launch argument

Requirements

Node, and the absolute path to each vault under Library/Mobile Documents/iCloud~md~obsidian/Documents/ — write the space in "Mobile Documents" as a plain space; the client hands the path straight to the server, so no backslash escape is needed. Run it from your own build: clone, npm install, npm run build, then point node at build/index.js with each vault path as an argument. The README's npx -y obsidian-mcp line does not fetch this project — on npm that name belongs to a different Obsidian server. It is fully tested on macOS only — the README asks Windows and Linux users to report whether it works.

Setup effort

Build from source — git clone https://github.com/YanceyOfficial/obsidian-mcp.git