Vault MCP
Related Servers
Alternatives to Vault MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceExposes a local Obsidian vault as a stateless MCP server, letting AI coding agents search, read, browse, and edit notes in real time.-
- FlicenseCqualityDmaintenanceMCP server to query and modify an Obsidian vault or any folder of markdown files. It provides search, tag filtering, backlinks, and CRUD operations on notes, with path traversal protection.11-
- AlicenseNot gradedqualityDmaintenanceMCP server for browsing Obsidian-compatible Markdown vaults, searching notes, viewing backlinks and knowledge graphs, and adding selected content to chat context.9 npmMIT
- FlicenseAqualityDmaintenanceMCP server that exposes an Obsidian vault to AI assistants, enabling them to list, read, write, search, and delete notes via the Local REST API.7-
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that exposes an Obsidian vault to LLM clients over Streamable HTTP, letting them browse the accessible tree, read notes, run full-text searches, and resolve wiki-links and backlinks within a share-filtered note set. Access is limited by an operator-editable sharing config that is default-deny and never writes to the vault.3,713 npmMIT
- AlicenseAqualityCmaintenanceA filesystem-based MCP server for Obsidian vaults that enables LLMs to browse, search, read, write, and edit Markdown notes directly on disk without requiring Obsidian to be running.61CeCILL-B Free Software Agreement
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing pages, reading a page, full-text searching, and finding broken wikilinks. Although list_pages and search both help locate pages, one is structural and the other content-based, so an agent can easily choose between them.
Two tools follow a verb_noun pattern (list_pages, read_page), but 'search' is a bare verb and 'broken_links' is a noun phrase. The mixed conventions are still readable, but they prevent a fully predictable pattern.
Four tools are well-scoped for a read-only Markdown vault interface. Each tool covers a distinct operation and none feels redundant or extraneous.
The surface covers listing, reading, searching, and link validation, but there are no write operations such as create_page, update_page, or delete_page. If the vault is intended to be editable, this is a notable gap; if strictly read-only, it is closer to complete.