I checked them all — mcp-obsidian, mcpvault, obsidian-mcp-server, obsidian-mcp-tools, obsidian-mcp-plugin. They read files. They write files. Some search. That's it.
None of them can create a visual diagram. None of them rank search results by relevance. None of them can tell an agent "here are the 12 themes in this vault and which files belong to which."
Local MCP server for Obsidian vault operations — search, intelligence, canvas tools
Sterne
14
Tools
—
Uptime
—
VaultForge does all three.
Feature
VaultForge
mcp-obsidian
mcpvault
obsidian-mcp-server
Read / Write / Delete notes
✅
✅
✅
✅
Full-text search
✅
✅
✅
✅
Edit in-place
✅
❌
✅
❌
Batch operations
✅
❌
❌
❌
Daily notes
✅
❌
❌
✅
Vault stats
✅
❌
✅
❌
Canvas — create with auto-layout
✅
❌
❌
❌
Canvas — semantic read
✅
❌
❌
❌
Canvas — patch (add/remove/update)
✅
❌
❌
❌
Canvas — re-layout (dagre)
✅
❌
❌
❌
BM25 smart search (Orama)
✅
❌
❌
❌
Vault theme mapping (TF-IDF)
✅
❌
❌
❌
Vault reorganization engine
✅
❌
❌
❌
Regex find-and-replace (grep-sub)
✅
❌
❌
❌
Batch rename / move with link updates
✅
❌
❌
❌
Backlink analysis
✅
❌
❌
❌
Frontmatter as structured data
✅
❌
❌
❌
Directory management (delete, prune)
✅
❌
❌
❌
No Obsidian plugin required
✅
❌
✅
❌
Fewer Tokens. Same Intelligence.
The other Obsidian MCPs weren't designed for AI agents — they were designed for humans who happen to use AI. Every tool returns raw, verbose data that burns through context windows. VaultForge is AI-infrastructure: every response is shaped to minimize token consumption while maximizing semantic density.
Agent reads files one by one (N calls × M tokens each)
One vault_themes() call returns clustered map
~95% fewer tokens
Tokens = API cost, context window space, and latency. Fewer tokens means faster, cheaper, smarter agents.
Three Things No Other MCP Can Do
🎨 Canvas Tools
The agent thinks in graphs. The tool thinks in pixels.
AI agents create, read, modify, and re-layout JSON Canvas files without touching a single coordinate. The agent describes a semantic graph. VaultForge calculates all geometry using dagre — the same Sugiyama layout engine behind Mermaid and React Flow.
canvas_create — describe nodes and edges, get a fully laid-out .canvas file:
Agent sends: Obsidian renders:
nodes: ┌───────────┐
- API Gateway │ API │───┐
- Auth Service │ Gateway │ │
- Database └───────────┘ │
- Cache ┌───────────┐ │ ┌───────────┐
edges: │ Auth │───┼──▶│ Database │
- API Gateway → Auth Service │ Service │ │ └───────────┘
- API Gateway → Cache └───────────┘ │
- Auth Service → Database │ ┌───────────┐
- Cache → Database └──▶│ Cache │
layout: { direction: "LR" } └───────────┘
A typical canvas with 15 nodes returns ~200 tokens as a semantic graph vs ~2,000+ tokens as raw JSON Canvas. The agent gets the same information at 10% of the cost.
canvas_patch — modify with relative positioning:
add_nodes: [{ label: "New Module", near: "API Gateway", position: "below" }]
remove_nodes: ["Deprecated Service"] → cascade-removes all connected edges
canvas_relayout — fix a messy canvas with one call. Preview before committing.
🔍 Smart Search
Not grep. Elasticsearch-grade.
Orama BM25-ranked search with typo tolerance, stemming (26 languages), and field boosting. No ML, no API keys, no internet.
smart_search("stripe webhook")
→ Stripe-Webhooks.md score: 0.92
"...webhook endpoint configuration for handling Stripe events..."
→ Refactor-Prompts.md score: 0.61
"...refactor the Stripe integration to use webhook signatures..."
vs search_content("stripe webhook")
→ Returns EVERY file containing "stripe", unranked, no scoring
Unranked grep forces the agent to consume every result to find relevance. BM25 puts the answer at the top. Fewer results read = fewer tokens burned = faster, cheaper responses.
Field boosting: title (3×) > tags (2.5×) > headings (2×) > content (1×).
Persistent index at .vaultforge/search-index.json — survives restarts.
🧠 Vault Intelligence
Your vault has folders. Now it has a map.
Files land where the energy of the moment puts them. Themes bleed across folders — "SpecForge" ends up in Projetos/, AI/prompts/, Content/, and Empresas/. Nobody maintains a perfect taxonomy.
vault_themes — scans every file, extracts distinctive terms via TF-IDF, clusters by similarity:
Without this, an agent needs to read_note on every file individually to understand vault structure — hundreds of tool calls, thousands of tokens. One vault_themes() call replaces all of them.
vault_suggest — actionable reorganization from the atlas:
What's coming next. Ordered by priority — community input shapes the sequence.
v0.6.0 — Vault Graph & Tags
vault_graph — Export the vault's link graph as a JSON adjacency list. Nodes = files, edges = wikilinks. Enables agents to reason about knowledge structure, find clusters, detect orphans, and identify bridge notes. Output compatible with D3, Cytoscape, or canvas_create for visual rendering.
tag_search — Search by YAML frontmatter tags, separate from content search. Filter by tag combinations (tag:draft AND tag:specforge). Returns files with matching tags plus their frontmatter metadata.
diff_note — Compare two notes (or two versions of the same note) and return a structured diff. Useful for agents reviewing changes, merging edits, or auditing vault history.
v0.7.0 — Template Engine & Smart Create
template_create — Create notes from templates with variable substitution ({{date}}, {{title}}, {{tags}}). Supports custom template folders. The agent describes intent, the tool handles boilerplate.
smart_create — AI-aware note creation. Analyzes vault themes and suggests optimal location, tags, and links for new notes. "Write about X" → creates the note in the right folder with relevant backlinks.
Parallel batch operations where order independence allows
Index compression for faster startup on large vaults
Benchmark suite with reproducible performance targets
v1.0.0 — Stability & Ecosystem
Comprehensive test suite with >90% coverage
Stable API — no breaking changes without major version bump
Plugin ecosystem hooks — allow community extensions
Published to MCP registry
Obsidian community plugin (optional companion for enhanced integration)
Community-Driven
Open an issue tagged roadmap to propose features. The most-requested items move up the queue. This is an open forge — the community shapes the steel.
The Forge is Open
VaultForge is the first open-source tool from the Blacksmithers — a community of builders who forge tools that build things.
We don't wrap APIs and call it innovation. We build real engines — BM25 search, graph layout, TF-IDF clustering — because the tools AI agents use should be as rigorous as the agents themselves.
If that resonates, you're already one of us.
Contributing
Open an issue first to discuss changes. PRs welcome — especially for:
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Vaultforge?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Vaultforge einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Vaultforge?
Vaultforge läuft lokal über stdio.
Wann wurde Vaultforge zuletzt geprüft?
Zuletzt geprüft: 2026-10-27. Local MCP server for Obsidian vault operations — search, intelligence, canvas tools