discover-list-vaultslisted

List all configured Obsidian vaults — active vaults with online status, latency, and metadata, AND disabled vaults (skipped by the disabledVaults config). Returns three fields: defaultVault, vaults[] (active), disabled[] (skipped). EN triggers: "list my vaults", "show me my Obsidian vaults", "what vaults do I have", "are my vaults online", "which vaults are active", "which vaults are disabled", "show me all vaults including disabled". FR triggers : "liste mes vaults", "montre mes vaults Obsidian", "quels vaults j'ai", "mes vaults sont-ils en ligne", "quels vaults sont actifs", "quels vaults sont désactivés", "montre tous mes vaults y compris les désactivés". Example / Exemple: EN: "list my Obsidian vaults" FR: "liste mes vaults Obsidian"
tboome33/obsidian-mcp-router · ★ 1 · AI & Automation · score 74

Install: claude install-skill tboome33/obsidian-mcp-router

# discover-list-vaults Call the obsidian-router `list_vaults` MCP tool. It takes no arguments. The tool pings every ACTIVE vault in parallel and returns: - `defaultVault` — vault used when calls omit a `vault` argument (resolved by the 5-tier cascade) - `configPath` — where the registry is loaded from - `vaults[]` — active vaults, each with `name`, `type` (local|remote), `baseUrl`, `online`, `latencyMs`, `missingApiKey`, `error?`, `isDefault` - `disabled[]` — vaults this session cannot use right now. NOT pinged. Each entry: `name`, `type`, `reason`, `awaitingDeclaration` — and that last field is the one that matters, because the array holds two different absences: - `awaitingDeclaration: false` — the operator said no: skipped by the `disabledVaults` config, or a malformed entry. Nothing the user does in a session changes it. - `awaitingDeclaration: true` — the vault is real, enabled and healthy; this router install has `vaultReach: "declared"` active and this workspace has simply never declared it. This is the case with a fix the user can act on in-session: `confirm_workspace_binding` binds this workspace to it (and opens it if its Obsidian is not running), which is what makes it answer. Never describe such a vault as unavailable — it is one call away, and `config.json` is not the way. `/bind-workspace` offers exactly these as candidates. ## Adapt the response to what the user asked - **"which vaults are active"** → render only the `vaults[]` table, ignore `disabled[]