meta-setuplisted

# meta-setup Walks the user through installing **obsidian-mcp-router** and replacing their existing `obsidian-rest` / `obsidian-tools` user-scope MCP entries with a single `obsidian-router` entry that routes to all configured vaults. ## When to use - The user says: "install the router", "replace the obsidian MCP with the router", "set up multi-vault Obsidian", "add a remote vault to Claude". - The user has more than one Obsidian vault (or plans to) and doesn't want to maintain one MCP entry per vault. ## Pre-requisites to verify 1. `node --version` ≥ 18. 2. `~/.claude/obsidian-mcp-router/config.json` exists with at least one entry in `portRegistry`. If not, run `node <router-repo>/scripts/setup-vault.mjs <vault-path>` first. 3. Obsidian is installed and at least one vault has the Local REST API + MCP Router Bridge plugins activated. ## Install steps ```bash # 1. Clone (pick a destination that fits your workflow — examples below). # Linux/macOS: git clone https://github.com/tboome33/obsidian-mcp-router.git ~/dev/obsidian-mcp-router cd ~/dev/obsidian-mcp-router # Windows (PowerShell): # git clone https://github.com/tboome33/obsidian-mcp-router.git "$env:USERPROFILE\dev\obsidian-mcp-router" # cd "$env:USERPROFILE\dev\obsidian-mcp-router" # 2. Install dependencies + create global symlink npm install npm link # 3. Verify the binary is callable obsidian-mcp-router --version ``` Ask the user upfront which directory they prefer if it's not obvious. Don't pick a