Obsidian Second Brain MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | No | Path to the Obsidian vault (alternative to storing in .obsidian-second-brain.json) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_memory_startA | Load the compact Obsidian project memory pack for this repo before meaningful work. Use this at session start, before bug fixes, before feature work, and before project health reviews. |
| project_memory_statusA | Check whether this repo is linked to an Obsidian project memory pack and list missing standard notes. |
| project_memory_log_bugB | Append a bug investigation or fix record to Obsidian. Use when a bug is identified, investigated, fixed, verified, or left blocked. |
| project_memory_log_featureB | Append a feature planning or implementation record to Obsidian. Use when starting, changing, completing, or deferring feature work. |
| project_memory_record_decisionA | Record a durable project decision in Obsidian. Use when the agent or user chooses an approach, rejects alternatives, changes scope, or decides deployment/release behavior. |
| project_memory_close_sessionA | Close the loop after meaningful work by appending a session record to Obsidian. Use before final response when code, docs, bugs, features, tests, or deployment status changed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: starting/ending sessions, logging bugs/features, recording decisions, and checking status. Descriptions clearly differentiate them, leaving no ambiguity.
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.
Six tools cover the essential operations for a project memory system without excess. Each tool serves a clear, non-redundant purpose.
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.