A
licenseA
qualityB
maintenanceEnables AI coding agents to read, write, search, and organize notes in an Obsidian vault directly via the filesystem.
13
3,358 npm
MIT
Obsidian Second Brain MCP
by dhaseeb-proj
Related Servers
Alternatives to Obsidian Second Brain MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides AI agents with direct filesystem access to an Obsidian vault for note management, task orchestration, context persistence, and git synchronization.2778 npm3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to explore, search, and manage local Obsidian vault documents with tools for document search, automatic frontmatter property generation, and attachment organization.57 npm2ISC
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store and retrieve durable memory as markdown notes in an Obsidian vault, with full-text and semantic search, wikilink graph operations, and human-auditable, editable storage.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to use Obsidian vaults as persistent, bidirectional knowledge workspaces with wikilink/backlink resolution, structured frontmatter/tag indexing, task aggregation, and Obsidian Headless Sync.11MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to maintain a structured Markdown or Obsidian memory vault with tools for reading, writing, searching, and organizing notes.MIT
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a distinct purpose: starting/ending sessions, logging bugs/features, recording decisions, and checking status. Descriptions clearly differentiate them, leaving no ambiguity.
Naming Consistency4/5
All tools share the 'project_memory_' prefix with verb_noun for most (close_session, log_bug, etc.). 'start' and 'status' deviate slightly (verb only and noun only), but the pattern remains highly predictable.
Tool Count5/5
Six tools cover the essential operations for a project memory system without excess. Each tool serves a clear, non-redundant purpose.
Completeness5/5
The tool set covers the full lifecycle of project memory: start, log (bugs, features, decisions), close, and status check. No obvious gaps for the intended domain.
Maintenance
ActivityInactive
ResponsivenessNo issues