big-brain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIG_BRAIN_VAULT | Yes | Absolute path to the markdown vault folder |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brain_overviewA | Orient yourself in the user's second brain: active projects with next tasks, overdue and upcoming tasks, unprocessed inbox items, and recently touched notes. Call this at the start of a session or when asked 'what am I working on?'. |
| search_notesA | Search the vault: full-text (titles boosted, fuzzy + prefix matching), fused with local semantic search when the vault has embeddings enabled. Filter by type (note/project/daily/person/reference/area), tag, folder prefix, or frontmatter status. |
| related_notesA | Find notes related to a given note, with reasons: direct links, shared link-neighbors, shared (rarity-weighted) tags, unlinked title mentions, and semantic similarity when embeddings are enabled. Use to pull surrounding context before working on a topic, or to find where a new note should link. |
| read_noteA | Read a note by path, title, alias, or filename (case-insensitive). Returns frontmatter and full body. |
| create_noteB | Create a markdown note. type decides the folder (note→notes/, project→projects/, person→people/, reference→reference/, area→areas/). Use [[wikilinks]] in the body to connect it to related notes — always link generously. |
| append_noteA | Append markdown to a note, optionally under a specific heading (created at the end if missing). The safe default way to add content without overwriting anything. |
| update_frontmatterA | Merge keys into a note's YAML frontmatter (set a key to null to remove it). Use for status, priority, due, area, tags, aliases. |
| replace_note_bodyA | Rewrite a note's entire body (frontmatter preserved). Prefer append_note for additions; use this only for deliberate rewrites/reorganizations. |
| archive_noteA | Move a note into the archive folder (the non-destructive alternative to deletion). Archived notes are excluded from search and listings by default. |
| captureA | Quick-capture a thought, link, or piece of information into the inbox for later processing. Use when something is worth keeping but you don't yet know where it belongs. |
| daily_noteA | Return today's daily note (or a specific date's), creating it from the daily template if needed. |
| daily_logA | Append a timestamped entry to today's daily note Log section. Use to record decisions, progress, and events as they happen — this builds the user's work journal. |
| list_notesA | List notes by folder, type, or tag, most recently modified first. Use for browsing; use search_notes for content queries. |
| note_linksA | Show a note's graph neighborhood: outgoing wikilinks (resolved and broken) and backlinks from other notes. Use to explore context around a topic. |
| list_tagsA | All tags in the vault with usage counts, most used first. |
| list_projectsA | List projects with status, open/done task counts, and next tasks. Statuses: idea, active, paused, done, dropped. |
| create_projectB | Create a project note (Goal/Tasks/Notes/Log sections) with status frontmatter. Projects are the unit of ongoing work; link related notes to them with [[wikilinks]]. |
| set_project_statusB | Change a project's status (idea/active/paused/done/dropped). 'done' stamps a completion date. |
| list_tasksA | List checkbox tasks across the vault, sorted by due date then priority. Filter by status (open/done/all), project, tag, or dueBy date. |
| add_taskA | Add a checkbox task to a project's Tasks section (or today's daily note if no note given). Supports due date and priority. |
| complete_taskA | Mark a task done by id (from list_tasks) or by a unique text fragment. Stamps today's date. |
| update_taskA | Edit one task in place: reschedule (due), reprioritize, reword, reopen, or cancel — without rewriting the note. Matches by id (from list_tasks) or a unique text fragment, including done and cancelled tasks. Use complete_task to finish a task. |
| vault_healthA | Lint the vault: broken wikilinks, duplicate titles, stale active projects, overdue tasks, orphan notes, inbox pileup. Use during reviews. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| orient | Load the vault overview and act as a second-brain-aware assistant |
| weekly-review | Run a guided weekly review of projects, tasks, and inbox |
| process-inbox | Triage unprocessed inbox captures into the right place |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Most tools target clearly distinct resources and actions (notes vs tasks vs projects vs daily notes), and descriptions actively steer between near-neighbors like append_note vs replace_note_body and list_notes vs search_notes. The main soft spot is note_links vs related_notes, both graph/context-exploration tools whose boundaries require reading the descriptions carefully.
All names use snake_case consistently, which keeps the set readable. However, verb-first (list_notes, create_note, update_task) is mixed with noun-first naming (note_links, related_notes, daily_note, daily_log, brain_overview, vault_health), so the pattern isn't fully predictable.
At 23 tools the set is on the heavy side, but the domain is genuinely broad (notes, tasks, projects, daily notes, search, graph, and vault health), and nearly every tool maps to a distinct operation. It is slightly over what one would want but not padded.
Coverage is strong: notes support create/read/append/replace/frontmatter/archive plus search, links, and related notes; tasks have add/complete/update/list; projects have create/list/status. Minor gaps remain, notably no unarchive/restore to pair with archive_note and no note move/rename operation.