cwa-book-mcp
Related Servers
Alternatives to cwa-book-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables browsing, searching, and quote verification of a local ebook library via MCP, providing deterministic RAG with no embeddings or network.625 PyPI2MIT
- FlicenseAqualityBmaintenanceEnables bibliographic research on a private local Calibre library by providing read-only metadata search, book inspection, and optional RAG-based content retrieval through MCP.5-
- AlicenseNot gradedqualityAmaintenanceEnables multi-source search and verified download of public-domain and open-license ebooks (Chinese/English) through a unified MCP interface.MIT
- FlicenseAqualityBmaintenanceEnables Claude clients to access a private local book library, allowing users to list books, search content, and retrieve metadata, chapter summaries, action items, personal notes, and infographic text through MCP tools.7-
- AlicenseAqualityCmaintenanceEnables MCP clients to search the Knihobot.cz public book catalog, inspect live physical copies, compare editions, and retrieve recommendations.5ISC
- AlicenseNot gradedqualityBmaintenanceEnables conversational management of a Calibre ebook library via MCP, including search, metadata editing, adding, converting, deduplicating, removing, and emailing books with human-in-the-loop safety.1MIT
TDQS
Scored across 6 tools
download_book and acquire_book overlap heavily — both take request_id, candidate_id, and required_format to create persistent tasks, and both expose retry/cancel semantics, so an agent could easily misselect between fetching the raw original versus the CWA-matched/converted copy. get_download_url and get_task are related status/retrieval tools but are more clearly separated by their resource. The distinctions exist but require close reading of dense descriptions.
All six tools follow a consistent verb_noun snake_case pattern: search_books, acquire_book, download_book, upload_book, get_task, get_download_url. The convention is predictable and uniform throughout, with no style mixing.
Six tools is well-scoped for a book-acquisition and library-management server. Sub-operations (retry, cancel, resolve, collect, prepare, refresh_ticket) are folded into action parameters rather than exploding into separate tools, keeping the surface lean and each tool earning its place.
The surface covers the core lifecycle: search sources, create acquisition task, get status, retrieve download URL, download original, and upload. Some operations an agent might expect as first-class tools (delete/remove from library, update metadata, list library) are absent or only implied, but the main workflows are covered.