bovedia
Related Servers
Alternatives to bovedia
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides Claude and other MCP clients with persistent memory through a Zettelkasten knowledge base of interconnected markdown notes. It enables LLMs to create, search, link, and reference atomic notes across sessions without requiring manual copy-pasting.MIT
- AlicenseAqualityBmaintenanceAn MCP server that stores notes as Markdown files on your machine, enabling you to save, search, and manage notes through natural language with Claude Code or Claude Desktop.5MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that serves a private markdown repository as a verifiable memory for Claude and other MCP clients, enabling tools to read, write, retrieve, and capture notes with deterministic verification of citations.292 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for reading and searching Markdown notes in any directory, such as an Obsidian vault. It integrates with MCP clients like Claude Desktop to access note contents.803 npm-
- AlicenseNot gradedqualityAmaintenanceProvides a local-first, file-based memory layer for Claude Code that syncs across machines via git over private networks, with MCP tools for search, write, and sync of human-readable markdown notes.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Sticky Rice - interact with your notes from Claude.5 npmMIT
TDQS
Scored across 36 tools
Each tool targets a distinct resource and action: read variants are separated by scope (full note, section, frontmatter, peek), write variants by operation (replace, append, prepend, section update), and audit tools by focus (vault health, tags, broken links, orphans). Even similar-sounding tools like list_tags, audit_tags, and prune_tags are clearly differentiated by their descriptions.
The vast majority of tools follow a clean snake_case verb_noun pattern (read_note, create_category, update_section, restore_snapshot). Minor deviations like vault_health and due_notes are noun/adjective phrases instead of verbs, and get_index uses 'get' while most list operations use 'list', creating a small inconsistency.
With 36 tools, the surface is too large for what is essentially one knowledge-vault server. Many tools are highly specific and could be consolidated, especially the section-level read/write variants and the overlapping tag-maintenance and health-audit tools, without losing meaningful capability.
The vault lifecycle is very well covered: notes, categories, links, tags, frontmatter, snapshots, and maintenance audits are all present. The only notable gap is that delete_note sends notes to a recoverable trash but no tool is exposed to list or restore from that trash, leaving a minor dead end.