Knowledge
Related Servers
Alternatives to Knowledge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to read and write to a personal knowledge vault of markdown notes, projects, and tasks, with tooling for search, capture, daily logs, and project management across different AI tools.2344 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants like Claude and Codex to read, write, search, and traverse Markdown notes stored in a self-hosted knowledge base.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to file notes into a self-hosted Obsidian vault and retrieve them later through structured and semantic search over plain Markdown.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and write a local-first Markdown/Obsidian notebook via a single capture call that routes text into the right notebook, board, or daily journal entry and returns related notes, alongside search, note and card management, and numeric metric series. Access is governed by per-agent tokens with read/write/admin scopes, optional folder restrictions, and an audit log of every action.MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to search, create, and manage notes in an Obsidian vault via 40+ local tools.5214 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to capture, search, update, and delete notes in a local Markdown vault with automatic categorization and tagging, making knowledge management seamless.6 npm1MIT
TDQS
Scored across 8 tools
Each tool maps to a distinct resource+action pair, and the suffix conventions (notes = list, note_get = read) plus explicit descriptions keep the list/read pairs separable. Minor overlap between open_notebook_search scoped to a notebook and open_notebook_notes listing within a notebook, but the descriptions clarify the boundary.
Seven of eight tools share the open_notebook_ prefix and snake_case, which is good. However, verb placement is mixed: noun_verb (open_notebook_note_get, open_notebook_source_get), verb_noun (open_notebook_add_source), and bare nouns (open_notebook_notebooks, open_notebook_notes), and the final tool (knowledge_modules) breaks the prefix entirely.
Eight tools is well within a comfortable range for a notebook/source/note management server. Each tool serves a distinct role: browsing, reading, searching, creating, and one meta/introspection tool.
Read paths and creation are covered (list notebooks, list/read notes, read sources, search, create note, add source), but there is no way to list sources belonging to a notebook and no update or delete operations for notes, sources, or notebooks. The surface supports ingestion and reading but leaves lifecycle management and source browsing as notable gaps.