F
licenseNot graded
qualityD
maintenanceProvides AI assistants with full-text search access to your Obsidian vault, allowing them to query, retrieve, and analyze notes through the Model Context Protocol.
3
-
Heptabase MCP
by LarryStanley
Related Servers
Alternatives to Heptabase MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI assistants with structured access to your Logseq knowledge graph, enabling retrieval, searching, analysis, and creation of content within your personal knowledge base.70-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI assistants with direct access to local document collections through full-text search, supporting multiple formats and hierarchical collections.MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol implementation that enables AI assistants to interact with markdown documentation files, providing capabilities for document management, metadata handling, search, and documentation health analysis.1457 npm58MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Obsidian vaults through vector search, vault indexing, and file monitoring. It provides a standardized interface for searching and managing markdown-based personal knowledge management data within the Model Context Protocol.11,823 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to read, search, create, and modify Obsidian notes via the Model Context Protocol, supporting tasks like daily notes, backlinks, and project management.-
TDQS
D1.6/5.0
Scored across 14 tools
Disambiguation3/5
The tools cover distinct domains like cards, whiteboards, and backups, but some overlap exists within domains. For example, getCard and getCardContent could be confused for retrieving card information, and searchCards/getCardsByArea might have unclear boundaries for finding cards. However, the domains themselves are well-separated, preventing major misselection.
Naming Consistency2/5
Naming is inconsistent with mixed conventions: camelCase (e.g., analyzeGraph, debugInfo) and snake_case (e.g., get_card_content, list_backups) are both used, and verb styles vary (e.g., 'configure' vs. 'load' vs. 'get'). This lack of a predictable pattern makes the set harder to navigate and less coherent.
Tool Count4/5
With 14 tools, the count is reasonable for a note-taking or knowledge management server like Heptabase, covering cards, whiteboards, backups, and analysis. It's slightly on the higher side but well-scoped, as each tool appears to serve a distinct function without obvious bloat.
Completeness3/5
The server shows notable gaps in coverage. For cards and whiteboards, there are read/search tools but no create, update, or delete operations, which are essential for a full CRUD lifecycle. Backup tools are more complete, but the core domain lacks write capabilities, potentially causing agent failures in workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues