knotlog
Related Servers
Alternatives to knotlog
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenancePersistent shared memory for AI coding agents that turns a folder of markdown files into searchable memory across sessions, repos, and machines.10 npmFunctional Source , Version 1.1, MIT Future
- AlicenseNot gradedqualityBmaintenanceGives coding agents a persistent memory by searching a local, read-only index of existing markdown and letting them write findings back as notes that the next session can retrieve. It serves ranked, context-sized results over MCP, injects standing conventions at session start, and keeps data on your machine with secret redaction and archive-only deletion.MIT
- FlicenseNot gradedqualityCmaintenancePersistent memory for AI agents enabling saving, searching, and managing knowledge across sessions with local markdown files.-
- AlicenseNot gradedqualityDmaintenanceProvides coding agents with persistent local memory by exposing tools to save, search, and retrieve decisions, bugs, and context as Markdown with hybrid keyword and semantic search.4MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.MIT
- AlicenseAqualityBmaintenanceProvides AI coding assistants persistent engineering memory stored as Markdown files in an Obsidian vault, enabling project context retrieval, session capture, decision recording, and memory search without requiring Obsidian to be running.71MIT
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.