Obsidian
The Obsidian connector indexes notes from local Obsidian vaults into the local SQLite index, including frontmatter tags and wikilink graph edges. It exposes read tools for listing, reading, and substring-searching notes across all configured vaults, plus one HITL-gated write tool for appending to today’s daily note.
This is a filesystem-only connector — no network call, no remote credential. Vault roots come from [[filesystem.roots]] in your nimbus.toml.
What’s indexed
Section titled “What’s indexed”- Service id:
obsidian - Item types:
obsidian_note - Graph: wikilink edges are also written to
graph_entity/graph_relationfor cross-note traversal.
Authenticate
Section titled “Authenticate”No credential. The Gateway discovers vaults by walking each [[filesystem.roots]] path for a .obsidian/ marker directory and exposes the discovered vault list to the MCP server as OBSIDIAN_VAULT_PATHS_JSON (a JSON array of absolute paths).
Read tools (no HITL)
Section titled “Read tools (no HITL)”| Tool | Purpose |
|---|---|
obsidian_get |
Read a single Obsidian note by id, or by (vault, path) pair. |
obsidian_list |
List Obsidian notes (optionally filtered by vault id, vault path, or frontmatter tag). |
obsidian_search |
Substring-match against note title and body across all configured vaults. |
obsidian_daily_note_get |
Read the end (at most the last 16 KiB) of the daily note obsidian_append_to_daily_note would write for the same vault and date. Nimbus shows it in the approval prompt before an append. |
Write tools (HITL-gated)
Section titled “Write tools (HITL-gated)”Every tool below requires interactive consent through the Gateway HITL gate before it executes.
| Tool | Purpose |
|---|---|
obsidian_append_to_daily_note |
Append text to today’s daily note. Creates the file if it does not exist. Always appends — never overwrites. Adds a leading newline when the existing file does not end in one. |
The append needs your opt-in. The connector runs in a sandbox that may only read your vaults. Run nimbus connector writes enable obsidian and approve it: the sandbox may then write one file in each vault, today’s daily note (the date in UTC), and nothing else (not .obsidian, not .git, no other note), and the prompt names each vault’s note pattern. Only while that approval stands can an append (from the model, or an MCP client’s proposal you accepted) reach the file, and only for today’s date. Each append still asks you first. nimbus connector writes disable obsidian withdraws it at once.
Platform notes
Section titled “Platform notes”- Local-only. Vault roots come from
[[filesystem.roots]]innimbus.toml. Vaults are auto-discovered by walking each root for a.obsidian/marker. - All paths are validated by
assertWithinVaultagainst directory traversal —..segments and absolute paths outside the vault root are rejected — and, since connectors 0.5.0, by their real path, so a daily-notes folder that is or passes through a link out of the vault is refused. - Links are not followed. Indexing skips every symlink or junction below a configured root (a linked folder inside a vault included), and never reads a note through a link, so a note outside your roots is never indexed by way of one. A root that is itself a link is followed.
- The sync also writes to the
obsidian_notestable and the graph tables (graph_entity/graph_relation) so wikilink follows work in agent searches.
Remote content in a model-written append is refused. For obsidian_append_to_daily_note written by the model (or proposed by an MCP client), Nimbus refuses the text, before it asks you, if the note would load remote content in reading view: a Markdown image ( or a reference image, even with a relative URL), inline HTML that loads something (an <img>, <iframe>, <link> or CSS url(), or a mermaid block holding a URL. Vault embeds (![[note]], ![[image.png|200]]), links ([text](url)) and autolinks stay allowed. Text holding a < followed by a letter that never closes (a <b) is refused too, because it cannot be read as markup.