hive
Related Servers
Alternatives to hive
- AlicenseNot gradedqualityNot gradedmaintenanceThis is a connector to allow Claude Desktop (or any MCP client) to read and search any directory containing Markdown notes (such as an Obsidian vault).797 npm1,352AGPL 3.0
Related Servers
- AlicenseAqualityFmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with secure access to Obsidian vaults. Enables reading, writing, searching, and managing notes without requiring Obsidian to be running.506,222 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceContext Portal (ConPort): A memory bank MCP server building a project-specific knowledge graph to supercharge AI assistants. Enables powerful Retrieval Augmented Generation (RAG) for context-aware development in your IDE.766Apache 2.0
- AlicenseAqualityFmaintenanceThis project implements a Model Context Protocol (MCP) server for connecting AI models with Obsidian knowledge bases. Through this server, AI models can directly access and manipulate Obsidian notes, including reading, creating, updating, and deleting notes, as well as managing folder structures.1156 npm311MIT
- FlicenseNot gradedqualityCmaintenanceExposes Obsidian vault tools via Model Context Protocol (MCP) server over stdio, HTTP, or SSE transports, enabling AI assistants to read, write, search, and manage vault notes with 28+ built-in tools and CLI bridge integration.1-
- AlicenseNot gradedqualityCmaintenanceMCP server for Obsidian vaults — multi-brain manager with templates, persistent registry, search, CRUD, frontmatter, wikilinks and context bundling. Works with Hermes Agent and Claude Code simultaneously.MIT
- AlicenseNot gradedqualityAmaintenanceA local-first MCP server that indexes Markdown/Obsidian folders and lets AI clients retrieve cited local context through MCP.MIT
TDQS
Scored across 13 tools
Most tools have a distinct role, but several retrieval paths overlap: vault_query, vault_search, vault_ask, and delegate_task can all be used to read or summarize vault content, and vault_search's lessons-only mode overlaps capture_lesson's lookup mode. vault_write/replace and vault_patch also offer close update paths, so the boundaries are clear only with careful reading.
The vault_* tools form a clear, consistent namespace and all names are readable snake_case. The set is not perfectly uniform, though: session_briefing and worker_status use domain-plus-noun, while capture_lesson and delegate_task use verb-first names, so the naming convention is cohesive but mixed.
Thirteen tools is a well-scoped size for this domain: content CRUD, search, git commits, health, session context, lesson capture, and worker visibility are all represented without obvious bloat. Each tool appears to earn its place.
The vault surface covers create, read, update, patch, delete, commit, search, health, session startup, lessons, and worker status, which is strong for the stated domain. Minor gaps remain for direct lesson edit/delete operations and file renames/moves, but those can be worked around with the existing vault write/delete tools.