Vault Mcp Tools
Give your agent full read-write access to an Obsidian vault for notes, search, tags, graph, and canvas workflows.
Overview
io.github.afable702/vault-mcp-tools is a MCP server for the Build phase that provides 35 tools to read and write an Obsidian vault including notes, search, graph, tags, and canvas.
What is this MCP server?
- 35 MCP tools for Obsidian vault operations
- Notes, search, graph, tags, and canvas coverage
- Requires OBSIDIAN_VAULT_PATH; optional REST token unlocks 3 bonus tools
- Bonus tools with REST: execute_command, list_commands, open_in_obsidian
- stdio (default) or HTTP transport; npm package vault-mcp-tools v1.0.1
- 35 MCP tools for vault operations
- 3 bonus tools when Obsidian REST API is configured
- Package version 1.0.1 on npm
What problem does it solve?
Agents cannot safely navigate your Obsidian knowledge base, so specs and research stay disconnected from automated coding sessions.
Who is it for?
Obsidian-first indie builders who want agent-native note search, graph insight, and canvas edits on a local vault path.
Skip if: Teams standardized on Notion or Google Docs only, or environments unwilling to set vault paths and optional REST tokens on disk.
What do I get? / Deliverables
Your agent can search, edit, link, and analyze vault notes—and optionally drive Obsidian via REST—for documentation-grounded builds.
- Agent-driven note CRUD, search, tags, and graph operations
- Optional in-app Obsidian command execution and open-in-app flows
Recommended MCP Servers
Journey fit
Obsidian is where many solo builders store specs and runbooks; deep vault MCP support lands in build/docs as the primary documentation shelf. docs fits note CRUD, linking, and graph traversal that mirror how builders maintain product knowledge bases.
How it compares
Full Obsidian vault MCP with 35 tools, not a single-note snippet skill or cloud wiki API.
Common Questions / FAQ
Who is io.github.afable702/vault-mcp-tools for?
Solo builders and small teams who document in Obsidian and want MCP agents to search, edit, and graph their vault like a first-class datastore.
When should I use io.github.afable702/vault-mcp-tools?
Use it when product specs, research, and runbooks live in Obsidian and you need agent tooling for notes, tags, canvas, and deep search during development.
How do I add io.github.afable702/vault-mcp-tools to my agent?
Install vault-mcp-tools from npm, set OBSIDIAN_VAULT_PATH to your vault root, add the stdio MCP entry in your client, and optionally set OBSIDIAN_REST_TOKEN for the three REST bonus tools.