knowledge-library-mcp
Related Servers
Alternatives to knowledge-library-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceExposes a clinic's knowledge base and structured records to Claude Desktop as callable tools, with read tools grounded with citations and write tools gated behind approval.4-
- AlicenseAqualityBmaintenanceEnables a shared persistent knowledge vault for Claude Desktop, allowing notes to be saved, retrieved, searched, updated, and deleted across Chat and Code tabs.542 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude clients to search, read, and write to a Markdown second brain vault via GitHub, with tools for retrieval, capture, and knowledge graph consistency.-
- AlicenseAqualityAmaintenanceEnables Claude clients to interact with an Obsidian vault as a knowledge graph, supporting full-text search, backlink traversal, neighborhood exploration, and note creation/append.4182 npm15MIT
- AlicenseAqualityAmaintenanceEnables Claude Code to read, create, update, and delete Claude Cowork/claude.ai projects and their knowledge documents, including syncing local folders to projects, with safety features like backups and overwrite protection.17MIT
- FlicenseAqualityCmaintenanceEnables semantic search, question answering with cited sources, and incremental reindexing of personal notes via MCP tools for Claude Code.3-
TDQS
Scored across 11 tools
Each tool maps to a distinct resource and action: areas, note content, searches, projects, and git operations are cleanly separated. Even the retrieval tools differ clearly by path-based access, guidance-specific lookup, and area-scoped listing.
All tools follow a consistent snake_case verb_noun pattern: list_* for collections, get_* for single items, create/update/append for mutations, and save/list for git workflow. The naming makes the tool set predictable and easy to navigate.
11 tools is well-scoped for a knowledge library covering capture, search, retrieval, editing, project listing, and git persistence. Each tool serves a clear purpose without redundancy or bloat.
The surface covers create, read, update, search, capture, project listing, and git commit/push workflows. Missing delete/archive and a general list-all-notes operation are workable gaps, but they may be intentional for a permanent knowledge base.