second-brain-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_PATH | Yes | Absolute path to the vault root. Required, no default. | |
| MCP_AUTH_TOKEN | No | Static bearer token required for HTTP transport. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesB | List notes matching a glob pattern. Returns paths and mtimes only, no bodies. Excludes dotfiles and dotdirs. |
| read_noteB | Read the full content of a note at the given relative path. |
| write_noteC | Write content to a note. mode: 'create' | 'overwrite' | 'append'. |
| search_vaultB | Search the vault using ripgrep. Returns matching lines with file paths. |
| move_noteC | Move a note from one path to another. Both paths are relative to vault root. |
| capture_thoughtC | Capture a raw thought into raw/thoughts/ with frontmatter and tags. |
| list_task_sectionsB | List current section headers (##) in Tasks.md live from the file. |
| add_taskC | Add a task under an existing section in Tasks.md. section is matched case-insensitively against live headers. |
| get_tasksC | Get structured tasks parsed from Tasks.md with overdue flags. |
| append_logC | Append an entry to human meta/log.md. |
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 10 tools
Tools are largely distinct: note operations (list/read/write/move), search, task management, and logging each have clear purposes. However, write_note overlaps with capture_thought and append_log (all write operations), and list_notes vs search_vault both retrieve note information, requiring careful reading to choose correctly.
All tool names follow a consistent verb_noun snake_case pattern (list_notes, read_note, write_note, search_vault, move_note, capture_thought, list_task_sections, add_task, get_tasks, append_log). Minor singular/plural variation (note vs notes) exists but the pattern is predictable and readable.
10 tools is well-scoped for a personal knowledge management server. Each tool covers a distinct function within note handling, search, task management, or logging, with no redundant tools and sufficient breadth for the domain.
Missing delete_note and update_note (write_note can overwrite but no delete), and task management lacks complete/update/delete task operations. No way to create a new task section either. These gaps will force agents to fall back to generic write_note for editing Tasks.md, which is error-prone.