AI Books MCP Server
Related Servers
Alternatives to AI Books MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceExtends large language model context length up to 60 times using gravitational memory, designed for Claude Code and Anthropic AI models.813 npm2MIT
- AlicenseNot gradedqualityDmaintenanceVirtual Infinite Context for Agents and LLMs - maintains a continuous rolling context window, surfacing relevant memories while respecting token budgets.6MIT
- AlicenseAqualityBmaintenanceDeterministic, local-first context optimization for AI coding agents. Automatically compresses raw development session data (messages, tool logs, error stack traces, and git diffs) into a compact, task-specific context window. Operates 100% locally with zero external LLM dependencies, ensuring your source code never leaves your machine.6136 npmMIT
- AlicenseAqualityBmaintenanceNext-gen AST codebase map, token compression (70%~85% savings), and context packaging engine for AI coding agents & IDEs.43MIT
- AlicenseAqualityDmaintenanceEnables any LLM to process arbitrarily long contexts through recursive decomposition, without requiring external LLM APIs.1718 npm15MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first, cross-session context store that reduces token usage by saving facts, decisions, and preferences, and recalling them in later sessions with token-efficient ranking and compression.6 npmMIT
TDQS
Scored across 8 tools
Most tools have clearly distinct roles (create, list, delete, stats, verify), but query_knowledge_library and search_documents overlap in retrieving relevant chunks, requiring careful description reading to pick the right one.
The naming mostly follows a verb_noun pattern with consistent snake_case, but extend_context_from_files and search_documents deviate slightly from the knowledge_library-centric naming convention.
8 tools is well-scoped for a knowledge library server, covering creation, retrieval, management, integrity verification, and file-based context extration without unnecessary bloat.
The tool surface covers the core library lifecycle—create, list, query, delete—plus validation and file-based context loading. An update/add-to-existing-library operation is not present, but the domain appears adequately covered for typical use cases.