mysharedbrain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_DIR | No | Directory for the markdown vault (default: ./vault) | ./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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_noteB | Create a new markdown note. Folders are created from the id path. |
| read_noteB | Read a note by id. |
| update_noteC | Replace a note's content by id. |
| delete_noteC | Delete a note by id. |
| move_noteC | Move/rename a note. |
| search_notesC | Search notes by name and content (ripgrep). |
| give_feedbackA | Queue feedback: correct info, flag missing info, or file a request. kind is one of: correction | missing | request. |
| ask_questionB | Ask the librarian. Answered from the vault when possible, otherwise logged as missing information for future retrieval. |
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 8 tools
Core note CRUD tools are clearly distinct by action and resource, and search/move are well differentiated. Minor overlap exists between update_note and move_note, and between give_feedback and ask_question when logging missing information, but descriptions largely resolve this.
All tools follow a consistent snake_case verb_noun pattern: create_note, read_note, update_note, delete_note, move_note, search_notes, give_feedback, ask_question. The convention is predictable throughout.
Eight tools is well-scoped for a note vault with feedback and question support. Each tool has a clear, non-redundant purpose and the set is neither thin nor bloated.
The server covers full note lifecycle: create, read, update, delete, move/rename, and search, plus feedback and question channels. A list_notes or folder-listing operation is missing, but search may serve as a workaround for most discovery needs.