Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चmcp-name: io.github.epistates/turbovaultTurboVault is an MCP server that gives AI agents safe, fast access to Obsidian vaults, and a set of Rust crates for working with Obsidian Flavored Markdown. It's a single binary with no runtime dependencies.
git pull are always seen, even on network and cloud-synced vaults where file watchers report nothing..obsidian, .git) are unreachable, and network transports require authentication.Prebuilt binaries. Each GitHub release has archives for Linux (x86_64 and aarch64, glibc and musl), macOS (Intel and Apple silicon) and Windows (x86_64), built with every feature. Each archive has a .sha256 file and a signed build provenance attestation:
gh attestation verify turbovault-x86_64-unknown-linux-gnu.tar.gz --repo Epistates/turbovault
From crates.io:
cargo install turbovault # stdio only, all you need for Claude Desktop and Claude Code
cargo install turbovault --features release # what the prebuilt binaries have
Other features: http, websocket, tcp, full (all cross-platform transports), unix, sql (SQL over frontmatter) and vector-search (the vector search plugin).
Docker: ghcr.io/epistates/turbovault:<version> (amd64 and arm64). Mount the vault at /var/obsidian-vault:
docker run -i --rm -v "$HOME/Documents/Vault:/var/obsidian-vault" ghcr.io/epistates/turbovault:4.0.0
MCP Registry: listed as io.github.epistates/turbovault, with cargo and OCI packages.
Claude Code:
claude mcp add turbovault -- turbovault --vault ~/Documents/Vault
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"turbovault": {
"command": "/path/to/turbovault",
"args": ["--vault", "/path/to/your/vault", "--profile", "production"]
}
}
}
Leave out --vault to start with no vault and let the agent register one with add_vault. Runtime-registered vaults are remembered across restarts. For several vaults, a Git backend or per-vault settings, use a config file: see config.example.yaml and the configuration guide.
A good first call is get_vault_context: it returns the registered vaults, the active vault's counts and health, and the tools grouped by task.
tools/list shows the core tools by default. The ones marked (advanced) are callable by name all the same, and listed with --show-advanced-tools (see the configuration guide). Every tool that works inside a vault takes an optional vault argument naming the registered vault to run against; without it, the active vault. Coming from 3.x, docs/migration/4.0.md maps every old tool name to its replacement.
get_vault_context: Start here: vault status, health, the markdown dialect and the tools by taskread_note: Note content (whole, or by lines and sections) with the hash for conflict detectionwrite_note: Create, overwrite, append or prepend (auto-creates directories)edit_note: Surgical edits via SEARCH/REPLACE blocksdelete_note: Delete a note, refusing while other notes link to it (or striking their links through)move_note: Rename or relocate a note; Git-backed vaults atomically rewrite incoming wikilinks, Markdown links and canvas referencesget_notes_info: Existence, size, modified time, chosen frontmatter values and tags for several notes at oncemove_file (advanced): Move or rename any file, such as an image or PDFdiff_notes (advanced): Unified diff between two notes, or between a note and an audited versionbatch_execute: One all-or-nothing commit with write_backend: git; direct stays sequentialfanout (advanced): begin, commit or abandon an isolated Git worktree for long or parallel worklist_orphan_fanouts (advanced): Worktrees left behind by interrupted sessionsget_links: A note's backlinks (incoming, canvases included) or outgoing linksget_related_notes: Multi-hop graph traversalgraph_report: One list about the graph: hubs, centrality, dead_ends, isolated_clusters, cycles or broken_linksvault_health: 0-100 health score with counts; depth: full adds dead-end and hub countsexplain_vault: Holistic overview of structure, health, hubs and next actionssearch: BM25 search by keyword, narrowed by tags, frontmatter and folders, or related_to a notefind_similar: Notes about a topic or like a given note, by TF-IDF meaning rather than exact wordsquery_metadata: One frontmatter condition (equals, contains, >, <), with each match's frontmatterfind_duplicates (advanced): Near-duplicate pairs across the vaultcompare_notes (advanced): How alike two notes are and how strongly the graph links themsuggest_links (advanced): Notes a note could link to, with reasonsupdate_frontmatter: Patch frontmatter fields (merge or replace)manage_tags: Add or remove frontmatter tagsinspect_frontmatter (advanced): Frontmatter as SQL columns (feature: sql)query_frontmatter_sql (advanced): Read-only SQL over frontmatter, tags and links via GlueSQL (feature: sql)read_canvas: Read a .canvas (JSON Canvas 1.0): nodes, edges and the notes it points atwrite_canvas: Create or replace a canvas, validated against the spec and written the way Obsidian writes itquery_base: Run a .base file's filters, formulas, sort, grouping and limit over the vault's notesquery_tasks: Find tasks by status, due and scheduled dates, tag, folder, priority and text (Tasks plugin emoji and Dataview fields)get_periodic_note: Find or create the daily, weekly, monthly, quarterly or yearly note, using the vault's Daily notes or Periodic Notes settingsvalidate_vault: Problems Obsidian would trip on (pre-1.9 tags/aliases, bad frontmatter, broken links), by note and severity, for one note or the vaultnote_quality (advanced): Quality score for one note, or the vault-wide reportfind_stale_notes (advanced): Notes not modified within a threshold of daysanalyze_grounding (advanced): A note's claims and citations for an external judge, or the vault's uncited notesokf_validate (advanced): Validate the vault as an OKF v0.1 bundle; usable as a CI gategenerate_index (advanced): Generate or refresh index.md files for progressive disclosure (idempotent)append_log_entry (advanced): Append a dated entry to a folder's log.md (OKF section 7)visualize (advanced): Render the graph as a self-contained HTML filelist_templates: Available templates with their fields, or one by template_idcreate_from_template: Render and write a templated notefind_notes_from_template (advanced): Notes created from a templateget_ofm_guide: The Obsidian Flavored Markdown quick_ref, full syntax guide or an example notelist_vaults: Registered vaults and the active one; with name, that vault's full configurationadd_vault: Register a vault folder at runtime, or create: true to create it firstset_active_vault: The vault tools use when a call names noneremove_vault (advanced): Unregister a vault (its files are untouched)audit_log (advanced): Change log with operation ids, or summary: true for statistics and the hash-chain checkrollback_preview (advanced): What a rollback would change (read-only)rollback_note (advanced): Undo a change by operation id (audited, itself undoable)export (advanced): A health, broken_links, stats or analysis report as JSON or CSVobsidian://note/{vault}/{path}: listed, read as markdown, and subscribable. Subscribers hear when a note changes, whether TurboVault or another editor changed it.triage_vault, repair_broken_links, review_period, summarize_note and ground_draft, with completion for their arguments.delete_note, a move_note that replaces a note, a forced rollback_note, a batch_execute that deletes or replaces notes, and add_vault ask the user to confirm when the client supports elicitation. --no-confirm-destructive turns this off.On the default (direct) backend, each write is a temp file and an atomic rename, held to the note's expected_hash so an edit made since the last read is never lost. A batch applies in order and reports exactly what landed if it stops partway.
On a Git-backed vault (write_backend: git), every write is one commit and every batch is one all-or-nothing commit, with compare-and-swap on the branch so concurrent processes can't interleave. TurboVault refuses to overwrite files with uncommitted changes, and if writing out a commit is interrupted, the next write or the next start finishes it. fanout gives an agent a private worktree for long or parallel work, merged back or thrown away as a unit.
Every change is recorded in a hash-chained audit trail under .turbovault/ (or as Git history), and rollback_note undoes one, refusing to discard a later edit unless forced.
add_vault never accepts a filesystem root, the home directory, hidden or application-data directories under it, or system directories. --allowed-vault-roots limits it to chosen directories; on network transports it's off unless roots are set..obsidian, .git, node_modules and TurboVault's own .turbovault are unreachable through the note tools on both backends. A vault can protect more folders, never fewer.--auth-mode), with per-client rate limiting, and won't listen beyond loopback without authentication. WebSocket and TCP stay on loopback. The Unix socket lives in a private directory.--profile read-only refuses every mutating tool; allowed_operations: read makes one vault read-only.query_frontmatter_sql runs only SELECT, for at most 10 seconds and 1000 rows.Report vulnerabilities through GitHub private vulnerability reporting.
Logs go to stderr as JSON on stdio (RUST_LOG overrides the profile's level). --otlp-endpoint exports traces over OTLP, --metrics-port serves Prometheus metrics on 127.0.0.1, and every tool call is a span with the tool, vault, outcome and duration, never its arguments or note content.
Measured on synthetic vaults with a release build over MCP stdio:
The search index persists in TurboVault's cache directory, so a restart re-indexes only notes that changed.
Wikilinks ([[note]], [[note|alias]], [[note#heading]], [[note#^block]], and the table-escaped \|), embeds, Markdown links (inline, reference-style and percent-encoded), tags (#tag, #parent/child), tasks (including Tasks plugin emoji and Dataview fields), callouts, YAML frontmatter as Obsidian 1.9 reads it, properties with links, headings, JSON Canvas 1.0 and Bases.
git clone https://github.com/epistates/turbovault.git
cd turbovault
cargo build --release # ./target/release/turbovault
cargo test --workspace --all-features
Rust 1.90 builds the crates; the test suite needs 1.93.1 or later. See CONTRIBUTING.md and the development guide.
4.0 consolidates 79 tools into 52, adds the per-call vault argument and hides the advanced tools from tools/list by default. docs/migration/4.0.md maps every old tool and parameter to its replacement, and the changelog lists every library API change.
MIT. See LICENSE.
Markdown and OFM SDK w/ MCP server that transforms your Obsidian vault into an intelligent knowledge system
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Turbovault stdio पर लोकल चलता है।
पिछली जाँच 2026-10-26 को हुई। Markdown and OFM SDK w/ MCP server that transforms your Obsidian vault into an intelligent knowledge system