A
licenseB
qualityF
maintenanceA server that consolidates 21+ Obsidian tools into 5 intelligent operations (vault, edit, view, workflow, system) with contextual workflow hints to help AI agents effectively interact with Obsidian.
5
26 npm
36
MIT
mcp-obsidian-planner
by jarero321
Related Servers
Alternatives to mcp-obsidian-planner
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA comprehensive MCP server for Obsidian with 45 tools across hybrid filesystem-native and API-based architectures, enabling note management, backlinks, tag management, and analytics.638MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Obsidian that enables canvas creation with auto-layout, BM25-ranked search, vault theme mapping, and 27 tools for managing notes, files, and links.7 npm14MIT
- AlicenseBqualityFmaintenanceEnables seamless integration between AI models and Obsidian knowledge bases with 25 advanced tools for note management, intelligent search, AI-powered content analysis, auto-linking, tag management, template systems, and knowledge graph generation.2522 npm26MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that wraps the official Obsidian CLI to allow AI agents to read, write, search, and manage notes within an Obsidian vault. It provides 16 specialized tools for comprehensive vault interaction, including note management, task tracking, and metadata manipulation.1613MIT
- FlicenseBqualityBmaintenanceTurns a local Obsidian vault into a second brain with 27 MCP tools for capture, search, distillation, and review, all offline with no API keys or model calls.27-
TDQS
A3.6/5.0
Scored across 17 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no ambiguity. For example, daily_create, daily_get, and daily_set_focus all target different operations on daily notes, while inbox_add, inbox_list, inbox_prioritize, and inbox_process handle distinct inbox management steps. The tool set avoids overlap, making it easy for an agent to select the correct tool.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern throughout, such as daily_create, inbox_add, note_read, and project_create. All tools use snake_case with clear, descriptive names that indicate both the resource and action, providing a predictable and readable naming convention across the entire set.
Tool Count5/5
With 17 tools, the count is well-scoped for a planner application covering daily notes, inbox management, projects, tasks, and vault operations. Each tool earns its place by addressing specific needs in the domain, such as creating, reading, listing, and updating various elements, without being excessive or insufficient for the server's purpose.
Completeness5/5
The tool set provides complete CRUD/lifecycle coverage for the planner domain, including creation (e.g., daily_create, project_create), reading (e.g., daily_get, note_read), updating (e.g., daily_set_focus, task_toggle), and deletion (implied in inbox_process). It covers all core workflows from inbox capture to project management and weekly reviews, with no obvious gaps that would cause agent failures.
Maintenance
ActivityInactive
ResponsivenessNo issues