hardcover-mcp
Related Servers
Alternatives to hardcover-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI assistants to search the Hardcover book catalogue and manage personal library data, reading progress, reading statistics, goals, activities, and more through natural language.251MIT
- FlicenseAqualityCmaintenanceEnables AI assistants to interact with BookLore self-hosted libraries, allowing natural language queries to search books, manage reading status, ratings, series, authors, and highlights.71-
- AlicenseNot gradedqualityCmaintenanceEnables Claude, ChatGPT, and other MCP clients to read and manage a Hardcover account's library, reading progress, reviews, journal, lists, goals, follows, and notifications through 53 read/write tools. It is a hosted remote server that connects each user to their own account via Hardcover's OAuth sign-in, with six raw GraphQL tools reaching anything else in the API.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to help users manage their reading experience by searching books, tracking reading progress, managing bookmarks, and generating personalized recommendations and summaries.-
- AlicenseAqualityDmaintenanceConnects AI assistants to the Open Library API for searching books and authors, retrieving metadata, and comparing works.1255 npmMIT

SPINES MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to search books, manage reading lists, and access book collections and bookshelf data from SPINES via the Model Context Protocol.1149 npmMIT
TDQS
Scored across 28 tools
Tools are cleanly separated by resource and action, e.g. get_book vs get_user_book, get_user_library vs get_list, and get_activity_feed vs get_reading_journal. Descriptions explicitly route between near-neighbors, so no two tools appear to do the same job.
All names use snake_case with a predictable verb_noun shape: get_*, set_*, delete_*, and search_*. The broad use of set_ for create/update/upsert is applied consistently across the server.
At 28 tools, the surface is heavy, but it spans many Hardcover subdomains: catalog, library, reads, goals, lists, journal, social, prompts, and discovery. Most tools cover distinct operations, so it is borderline rather than clearly bloated.
CRUD/lifecycle coverage is strong for library entries, reads, goals, lists, and journal entries, with discovery and social flows also represented. Minor gaps remain, such as reordering existing list books or editing prompt-answer descriptions, and no standalone character/edition retrieval beyond embedded options.