obsidian MCP: document vault paths across CT 104/105/UNAS
This commit is contained in:
@@ -346,9 +346,13 @@ Complete reference for all 30 MCP servers managed by the gateway at `https://mcp
|
||||
| **Internal upstream** | `http://mcp-obsidian:8000` |
|
||||
| **Transport** | streamable-HTTP |
|
||||
| **Cache TTL** | 30 s |
|
||||
| **Vault path** | Nextcloud `fkrebs@nucli.de/files/Notizen` (UNAS mount) |
|
||||
| **Credentials** | inherits Nextcloud credentials from gateway env |
|
||||
| **Notes** | Vault read/write against the Nextcloud-mounted Obsidian vault. |
|
||||
| **Vault path (container)** | `/vault` |
|
||||
| **Vault path (CT 104 host)** | `/mnt/pve/unas/services/nextcloud/fkrebs@nucli.de/files/Notizen` |
|
||||
| **Vault path (CT 105 Nextcloud)** | same — both CTs bind-mount UNAS via `/mnt/pve/unas` |
|
||||
| **Vault path (UNAS NFS)** | `192.168.1.31:/var/nfs/shared/storage/services/nextcloud/fkrebs@nucli.de/files/Notizen` |
|
||||
| **Nextcloud-visible path** | `fkrebs@nucli.de` user → `Notizen/` folder (sync target for Obsidian desktop/mobile) |
|
||||
| **Credentials** | filesystem access only; no Nextcloud API needed |
|
||||
| **Notes** | Vault is the canonical Obsidian store, written by Nextcloud sync from desktop/mobile clients and read/written by the MCP server. Backed up via Backrest media/services plans (UNAS coverage). |
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user