second_brain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SECOND_BRAIN_VAULT | No | Absolute path to the Second Brain vault to use. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| second_brain_searchA | Search long-term memory before answering or acting on user preferences, project history, prior decisions, tools, or recurring workflows. Results are candidates; read the note before consequential use. |
| second_brain_readA | Read a Markdown note returned by second_brain_search. Hidden tool/config paths are blocked; 01_Sources is readable but never writable. |
| second_brain_core_contextA | Return the compact core-principles context used by the SessionStart hook. |
| second_brain_statusA | Report readable Markdown counts and the latest modification time without changing the vault. |
| second_brain_captureA | Save text explicitly marked by the user for retention into 00_Inbox/WorkBuddy. The tool redacts common credentials, is idempotent by content, and cannot write the evidence or knowledge layers. |
| second_brain_upsert_cardB | Create or update one structured card in 02_Knowledge. It cannot delete, move, or write 01_Sources. After success, update the vault index/log as needed and make a focused git commit. |
| second_brain_task_startB | Append an auditable task-start envelope with authority and retrieval receipt. It never writes 01_Sources or promotes knowledge. |
| second_brain_record_eventA | Append one redacted action, result, failure, verification, or checkpoint event to the current task ledger. |
| second_brain_task_finishC | Append outcome, verification, reflection, and an optional lesson candidate. Unverified results remain candidates and cannot be promoted automatically. |
| second_brain_recall_experienceA | Retrieve prior task outcomes and lesson candidates by query, task type, project, outcome, or error signature. Results are candidates with evidence levels and a receipt. |
| second_brain_score_candidatesB | Rank candidates only when safe:boolean and bounded numeric evidence fields are explicit; invalid or unsafe candidates are held. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| second-brain | Load the compact long-term-memory rules and core knowledge from the local Obsidian vault. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| second-brain-core | Compact always-on memory context. |
| second-brain-index | The Obsidian knowledge routing index. |
TDQS
Scored across 11 tools
The tools separate reasonably well by layer: read/search for retrieval, capture for inbox writes, upsert_card for knowledge writes, and task_start/record_event/task_finish for ledger lifecycle. There is some conceptual adjacency between search and recall_experience, and between record_event and task_start/task_finish, but the descriptions clarify their distinct scopes.
All names use the predictable second_brain_ prefix and snake_case, which makes the set easy to scan. Most names are verb-led, but a few are noun-led (core_context, status, task_start), so the pattern is slightly mixed rather than uniform.
Eleven tools is well-scoped for a personal memory system with retrieval, capture, structured knowledge, task lifecycle, events, recall, and candidate ranking. Each tool appears to earn its place without excessive fragmentation.
The surface covers the core lifecycle: search/read, capture, upsert knowledge cards, task start/event/finish, experience recall, and candidate scoring. Minor gaps remain around explicit deletion/archiving/forgetting and index/log maintenance, though some restrictions appear intentional for safety.