vault-mcp
Related Servers
Alternatives to vault-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for managing a local, domain-agnostic knowledge base using Markdown notes with frontmatter. Enables AI agents to capture, read, search, link, and maintain notes with atomic writes and privacy controls.13MIT

Wenlanofficial
AlicenseAqualityAmaintenanceLocal-first personal wiki and memory server for AI agents. MCP clients can capture knowledge, retrieve context, read and maintain source-backed wiki pages, and carry project context between sessions.3389Apache 2.0- AlicenseAqualityAmaintenanceProvides AI agents with a local, private Markdown-based memory vault and SQLite search. Enables agents to search, read, list, and traverse linked knowledge pages via MCP with zero external runtime dependencies.78MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for persistent, compounding markdown wikis maintained by LLMs. Enables incremental knowledge base building with interlinked pages, search, and raw source management.27 npm1MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first knowledge base MCP server. Lets AI agents (Claude Code, Cursor, etc.) read and write your personal knowledge base through 20 MCP tools. Zero cloud dependency — all files stay on your machine.1,758 npm678MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI coding agents persistent, cross-session memory by letting them save task insights as atomic markdown knowledge cards with bidirectional links and recall relevant cards before starting new work. Stores everything as plain markdown files that can be browsed, searched, and synced across clients and devices via git, with no vector database or embeddings required.13 npmISC
TDQS
Scored across 11 tools
Tools are mostly distinct with clear purposes, but vault_backlinks and vault_traverse (backward direction) both return incoming links, which could cause misselection. However, descriptions clarify the difference: backlinks is a direct lookup, while traverse explores the graph with depth.
All tools share the vault_ prefix, and most follow a verb pattern (write, read, edit, delete, list, search, lint, traverse). However, vault_backlinks and vault_write_batch deviate from the verb-only convention, making the set slightly inconsistent.
11 tools cover a complete note management workflow: CRUD, batch, search, list, lint, and graph exploration. The number is well-scoped, neither overwhelming nor thin.
The tool set provides full coverage of the vault lifecycle: create, read, update, delete, rename, batch operations, search, and health/link analysis. There are no obvious dead ends or missing core operations.