annas-mcp
Related Servers
Alternatives to annas-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for searching and downloading from Anna's Archive for free via slow channels like LibGen and Sci-Net, without an API key.2-
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server for searching and discovering books using Anna's Archive and Goodreads datasets, enabling full-text search, ISBN/md5 lookup, similarity matching, and optional download URL retrieval.12 npm4MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for AI assistants to search and download ebooks from Z-Library and Anna's Archive, configured locally with automatic setup and download path.4AGPL 3.0
- AlicenseAqualityCmaintenanceAn MCP server that lets AI agents search and download books from z-library using the user's own account credentials.450 npm9MIT
- AlicenseAqualityBmaintenanceAn MCP server for the Internet Archive that enables searching the full text of digitized books, browsing the catalogue, and reading Wayback Machine captures. No API key or configuration required.6572 npm3MIT
- AlicenseAqualityBmaintenanceA local MCP server for managing saved Substack posts. Enables offline reading, searching, bookmarking, and unbookmarking of Substack content via CLI or MCP clients.18MIT
TDQS
Scored across 9 tools
The set splits cleanly along resource lines (book_*, article_*, metadata_search, account_status), and the descriptions explicitly carve out the subtle boundary between book_search (Anna's Archive files) and metadata_search (catalog records with no file). The article family is also well separated by intent: find, inspect, fetch, read. The only mild risk is an agent defaulting to metadata_search when it actually wants a downloadable file, but the descriptions call this out directly.
Eight of nine tools follow a predictable resource_prefix + operation pattern (book_search, book_details, book_download, article_search, article_details, article_download, article_read, metadata_search). account_status breaks the verb pattern slightly by being a noun-state name, but it remains unambiguous and readable.
Nine tools covering two domains (books and scholarly articles) plus account state, with no redundant entries. Each tool maps to a distinct step in the search-details-download/read lifecycle, which is well-scoped for this purpose.
Core workflows are fully covered: search, detail inspection, download, and full-text read for articles, plus catalog lookup for non-downloadable books and allowance diagnosis. Pagination and continuation are handled via next_args/next_search_args rather than separate tools, which is a reasonable design. Minor gaps exist around collection browsing and citation/export, but agents can work around them.