Obsidian Second Brain MCP
Related Servers
Alternatives to Obsidian Second Brain MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA local MCP server that wraps the Obsidian CLI to give AI assistants direct access to read, edit, and manage notes within an Obsidian vault. It enables advanced operations such as frontmatter property management, context-aware searching, and the execution of internal Obsidian commands.2-
- AlicenseBqualityDmaintenanceLocal-first MCP server for Obsidian vaults with 66 tools for reading, writing, searching, and managing notes, tasks, graphs, and more. Works without Obsidian running and requires no plugins.66MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Obsidian that exposes tools for reading/writing notes, managing frontmatter and tags, querying Tasks, semantic search, and interacting with Obsidian Bases, with shared local caching and support for various runtime modes.40Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that provides read and write access to an Obsidian vault by interacting directly with markdown files on disk. Supports searching, listing, reading, creating, editing, and appending notes without requiring any Obsidian plugins.3,358 npmISC
- AlicenseNot gradedqualityDmaintenanceProvides an MCP server that allows AI assistants to interact with Obsidian vaults, enabling reading/writing notes, managing metadata, searching content, and working with daily notes.37MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes Obsidian vault operations over HTTP via the Obsidian CLI, enabling note management, search, and daily note operations.1-
TDQS
Scored across 10 tools
Most tools target distinct resources and actions: read/create/update/organize for notes, daily_note for the daily note, manage_tasks for tasks, and vault_overview/search for broader queries. Slight overlap exists between update_note's task-updating feature and manage_tasks, but descriptions clarify the intended use.
The majority follow a verb_noun pattern (read_note, create_note, update_note, organize_note, manage_tasks, suggest_use_cases, run_obsidian_command, search_notes). Two exceptions, daily_note and vault_overview, use noun-based naming, creating minor but tolerable inconsistency.
Ten tools is well within the ideal 3-15 range and each tool covers a meaningful aspect of vault interaction without redundancy. The count feels appropriately scoped for a second-brain management server.
The server covers note CRUD (including trash), daily notes, task management, search, and vault-level analytics, covering primary workflow needs. Minor gaps exist such as no explicit list-all-notes operation (search compensates) and no permanent deletion by design, but the surface is largely complete.