knotlog
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOTLOG_VAULT | No | Path to your Knotlog vault. Set this to point at an existing vault so the MCP server reads and writes that 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| knotlog_searchB | Search the Knotlog vault notes (folded lexical plus BM25 ranking); returns matching notes with short snippets. |
| knotlog_contextC | Return the session memory context of the current Knotlog vault. |
| knotlog_noteA | Append one line to today's session reflection note in the Knotlog vault (append-only, the same as knotlog note); writes nothing else. |
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 3 tools
The three tools target clearly distinct operations: reading session context, appending a note line, and searching the vault. While context and search both retrieve information, their scope (session memory vs. lexical/BM25 vault search) is clearly stated. No plausible misselection between them.
All tools share the consistent `knotlog_` prefix, giving a predictable namespace. The suffixes mix nouns (context, note) with a verb (search), and the noun-style names are slightly ambiguous as to read vs. write, but the overall pattern holds.
Three tools is thin for a note/vault server, especially since retrieval is split between context and search while no tool fetches a full note. The set is minimal but leans toward under-scoped rather than well-scoped.
Core read/append/search workflows exist, and append-only writing appears intentional. However, there is no way to fetch a full note (search returns only snippets), list notes, or correct/delete an entry, which are notable gaps for a note-management domain.