Vortex Notes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VORTEX_NOTES_VAULT | No | Path to the paired Vortex Notes vault, as printed by `vortex-notes pair`. | |
| VORTEX_NOTES_NO_SEMANTIC | No | Set to 1 to skip embeddings and use keyword-only search (no model download). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | Search the vault with hybrid keyword + semantic search. Returns note paths, headings, and snippets. Use read_note for full content. |
| read_noteA | Read a note's full markdown content by vault-relative path. |
| write_noteA | Create a new markdown note. Fails if the path already exists — use edit_note to modify existing notes. |
| edit_noteA | Edit an existing note surgically: append, prepend, or find_replace (exact string). Prefer this over rewriting whole notes. |
| append_dailyA | Append a timestamped entry to today's daily note (or a given date). The right place for observations, decisions, and things to remember. |
| build_contextA | Load working context for a topic in one call: full content of the top-matching notes plus one hop of [[wikilinked]] notes as pointers. Prefer this over multiple search+read rounds when starting work on a topic. |
| rememberA | Record a durable fact in the shared memory (memory/*.md) as a dated bullet with a stable ^id. If it replaces an earlier fact, pass supersedes (the old fact's ^id, or a distinctive substring of it) — the old fact stays visible with strikethrough and a pointer to the new one. Use search_notes to find existing facts first. |
| recent_activityB | List notes modified in the last N days, newest first. |
| list_notesB | List note paths, optionally under a folder. |
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 9 tools
Each tool has a fairly distinct purpose, and descriptions explicitly steer between near-neighbors (write_note vs edit_note, search_notes vs build_context). The main soft overlap is the family of write paths — write_note, edit_note, append_daily, and remember all add content to different targets — but the docs make the targets clear enough that misselection is unlikely.
Most tools follow a clean verb_noun pattern (search_notes, read_note, write_note, edit_note, build_context, list_notes). Two outliers — the bare verb 'remember' and the adjective-style 'recent_activity' — break the pattern but remain readable and unambiguous.
Nine tools is well-scoped for a note vault server, covering discovery, reading, writing, memory, and recency without redundancy. Every tool maps to a genuine workflow step; nothing feels padded or missing at the count level.
The surface covers search, read, create, surgical edit, daily append, durable memory, and recency, which handles most agent workflows. However there is no delete, move, or rename operation, so note lifecycle management is a dead end once a note is created at the wrong path or needs removal.