second-brain-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SB_VAULT_PATH | Yes | Path to the Obsidian vault, e.g. "$PWD/examples/vault". |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| contextA | Start-of-session context: the vault rules (CLAUDE.md), Home, and notes relevant to a topic. |
| searchB | Search notes by keywords across names, frontmatter and content. |
| readB | Read one or more notes (frontmatter + body). |
| captureB | Drop a quick note in the Inbox to be filed later. |
| writeA | Create a new note. Fails if a note with that name already exists (use patch instead). |
| patchA | Edit an existing note: append (optionally under a section), replace exact text, or set frontmatter. |
| linkC | Link two notes to each other under a 'Related' section. |
| dailyB | Append an entry to today's Daily note. |
| archiveA | Move a note to Archive/ (there is no hard delete; history is kept). |
| healthB | Vault health: missing frontmatter, broken links, orphans, unfiled inbox, stale projects. |
| personB | Everything about a person: profile, org, connections, recent log, meetings, mentions. |
| upsert_personA | Create or update a person. Matches existing names and aliases to avoid duplicates. Only store email/phone when the user explicitly gives them to be stored. |
| log_interactionB | Log a conversation: Meeting note, a line in each attendee's Log, last_contact, and the Daily note. |
| connectA | Record how two people are connected. Writes both sides (inverse relation on B). |
| who_knowsC | Who do I know at an organization, and/or how am I connected to someone. |
| follow_ups_dueC | People whose follow-up date is overdue or within N days. |
| people_graphC | The people graph (nodes and connection edges), optionally filtered by org or context. |
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 17 tools
Most tools target clearly distinct actions (capture/write/patch/read/search/archive for notes, connect/log_interaction/who_knows/upsert_person for people). A few overlap: 'person' (everything about a person), 'people_graph', and 'who_knows' all touch the people graph and could be confused, and 'capture' vs 'write' are close. Descriptions mostly disambiguate these boundaries.
All names are consistently lowercase snake_case, so there is no casing chaos. However the forms are mixed: some are verbs (archive, search, read, capture, patch, connect), some are nouns (context, health, person, people_graph), and some are verb_noun (upsert_person, log_interaction, follow_ups_due), so the pattern isn't fully predictable.
17 tools is on the heavier end but justified by a broad domain spanning note CRUD, a people/relationship CRM, daily logs, and vault maintenance. Each tool maps to a distinct workflow, so few feel redundant, though it sits right at the boundary of 'heavy'.
Lifecycle coverage is strong: notes have capture/write/read/patch/search/archive/link, people have upsert/person/connect/who_knows/log_interaction/follow_ups_due, plus health and context helpers; delete is intentionally omitted. Minor gaps exist (no rename/move of notes, no unlink or inbox-filing operation), but agents can work around them via patch.