obsidian-vault-mcp
Related Servers
Alternatives to obsidian-vault-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to create, update, search, and manage project entities (milestones, stories, tasks, decisions, documents, features) stored as markdown files in Obsidian with automatic relationship tracking and progress overview.4 npmMIT
- FlicenseBqualityAmaintenanceA local, file-backed feature/bug board for projects, enabling Claude to read and write markdown boards (featurelist.md / buglist.md) directly in chat for task planning, bug logging, and velocity tracking.2172-
- FlicenseAqualityDmaintenanceEnables comprehensive management of Obsidian vaults with full CRUD operations, advanced search, link/tag extraction, backlinks discovery, frontmatter editing, and template-based note creation through natural language.16-
- AlicenseAqualityCmaintenanceEnables AI agents to store and retrieve project context, bugs, decisions, and session logs by reading and appending markdown files in a local Obsidian vault, without requiring any cloud services.6MIT
- AlicenseAqualityCmaintenanceProvides AI agents with per-project note organization inside a single Obsidian vault, enabling them to resolve, write, read, append, list, and search notes without overwriting existing content.62,778 npmMIT
- AlicenseBqualityCmaintenanceTask planning and tracking for AI agents with project-based organization and Obsidian-compatible markdown storage.136 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct operation on either bugs or features, with no overlap. Bug tools are separated by function (create, read by path, list, get highest priority, update status), and feature tools are similarly distinct.
All tool names consistently follow the verb_noun pattern using snake_case, e.g., list_bugs, write_feature_doc, update_bug_status. No mixed conventions or vague verbs.
9 tools is well-scoped for a project management vault MCP, covering both bugs and features with essential operations. The number feels neither too thin nor excessive.
Bugs have create, read (multiple forms), and update status, but no delete. Features have create and read, but no update or delete. These are notable gaps that could hinder agent workflows requiring full lifecycle operations.