Vault MCP Server
Related Servers
Alternatives to Vault MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLM clients to read, create, edit, delete, move, and search notes in local Obsidian vaults via direct filesystem access, including tag management and support for multiple vaults.22 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to search, read, and write notes in an Obsidian vault, including creating and updating notes in an inbox and syncing changes with Gitea/GitHub.MIT
- AlicenseNot gradedqualityBmaintenanceEnables listing, reading, searching, appending, patching, and deleting markdown notes in a local vault through MCP tools. Vault paths are resolved per call, with access outside the vault refused.44 npmMIT
- FlicenseAqualityDmaintenanceEnables interaction with multiple Obsidian vaults through natural language, supporting note operations, search, and vault management with both REST and filesystem backends.17-
- AlicenseAqualityBmaintenanceEnables AI assistants to search, read, link, query, create, edit, and safely rename notes in an Obsidian-style markdown vault, including BM25 search, backlinks, frontmatter queries, and dry-run link updates.10MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading, writing, searching, and surgical editing of Obsidian vault notes, tags, and frontmatter, plus workspace control, vault structure management, and native Excalidraw automation.Apache 2.0
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose: issue CRUD and staging, note reading and listing, vault search, status overview, and three separate Telegram webhook operations (check, set, poll). No two tools overlap in function or could be confused for each other.
All tool names follow a consistent verb_noun snake_case pattern (create_issue, read_note, list_issues, set_telegram_webhook, etc.). The verb consistently leads, making the action obvious and the object clear, with no mixed conventions or ambiguous abbreviations.
With 12 tools, the set is well-scoped for a vault management server. Each tool addresses a specific need in issue tracking, note access, search, and Telegram integration; none are redundant or excessive for the intended functionality.
The core issue lifecycle (create, read, update, move between stages, list) is complete, and note reading/searching is well covered. Minor gaps include the lack of an explicit delete operation for issues and no create/update/delete for notes, but these are likely intentional design choices for a vault-based workflow.