LibraryThing MCP for AI. Map book editions and pull raw metadata.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
LibraryThing MCP connects your AI agent to a massive bibliographic database. Pull exact book metadata, map all ISBNs across physical and digital editions, and check how thoroughly a title is cataloged.
You get raw publication data, community ratings, and coverage scores without writing custom scrapers.
What your AI can do
Get book coverage
Returns a zero-to-one score showing how completely the community has cataloged a specific book.
Get work
Pulls detailed metadata like author, review counts, and member totals for a specific book record.
Thing isbn
Finds every ISBN for all physical and digital editions of a single title.
Group every physical and digital format of a single title under one canonical record.
Pull exact author, publisher, and release date information for any known book.
Get a zero-to-one score showing how completely the community has documented a specific title.
Grab member counts, review totals, and user-generated tags for any work.
Translate a messy book query into a stable internal ID for downstream lookups.
Ask an AI about this
Waiting for input…
LibraryThing MCP (4 Tools)
Use these four tools to resolve book identifiers, map different editions to a single canonical record, and pull detailed publication metadata.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using LibraryThing on VinkiusGet Book Coverage
Returns a zero-to-one score showing how completely the community has cataloged a specific book.
Get Work
Pulls detailed metadata like author, review counts, and member totals for a specific...
Thing Isbn
Finds every ISBN for all physical and digital editions of a single title.
What Work
Translates a basic book query into the internal ID required for deeper lookups.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with LibraryThing, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by LibraryThing. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Scraping book data is a miserable way to spend a Tuesday.
You need publication dates and edition mappings for a new feature. You open a browser, search for the book, and copy the ISBN. Then you open another tab to check the paperback version. You paste the data into a spreadsheet. You do this for fifty books. The formatting breaks. The publisher names are inconsistent. You spend three hours just cleaning up the text.
Now you just tell your agent to pull the data. It grabs the exact metadata, maps every edition automatically, and drops it into your database as clean JSON. You get back to writing actual code instead of fighting with copy-paste.
LibraryThing MCP gives you clean bibliographic records.
You no longer have to manually cross-reference hardcover and paperback ISBNs to figure out if they are the same book. You do not have to guess if a title has enough community reviews to be useful. The manual translation between messy retail identifiers and clean database records is gone.
You get a direct pipeline to a massive, community-maintained book database. Your agent handles the lookups, resolves the IDs, and returns exactly what you asked for.
What your AI can actually do with this
Look, if you are building an app that relies on book data, you know the pain. You either pay for a massive commercial API or spend weeks writing fragile web scrapers that break when a site changes its layout. This MCP gives you a direct line to the LibraryThing database.
You just ask your agent to find a book, and it pulls the exact metadata, community ratings, and publication history. Because Vinkius hosts this connection, you skip the boilerplate of setting up HTTP clients and parsing messy HTML. You just plug it into your preferred client and start querying.
It handles the messy part of bibliographic data. Books have dozens of editions. A single title might have a hardcover, a paperback, an audio version, and five international releases. This tool maps all those variations back to a single canonical work. You get a clear picture of what actually exists in the real world, plus a coverage score that tells you how well the community has cataloged it.
It is basically a shortcut to clean, normalized book data.
019d84b3-5cc4-7094-8fe0-07b39f2af67a Here's how it actually works
The bottom line is you get instant access to a massive, community-maintained book database without writing a single line of parser code.
Subscribe to the MCP and generate a LibraryThing Developer Key from their services page.
Connect your AI client using the provided configuration and paste in your API key.
Ask your agent to look up a book by ISBN or title to start pulling bibliographic data.
Who is this actually for?
This is for the backend engineer tired of scraping Amazon, the data scientist building a recommendation engine, and the digital librarian who needs accurate edition mapping without spending hours on manual data entry.
Writes the integration code that pulls clean JSON book metadata directly into the app database.
Feeds historical publication data and community ratings into a book recommendation model.
Maps obscure international editions to their canonical works to fix cataloging errors.
What Changes When You Connect
Stop guessing which edition a user meant. The thing_isbn tool maps every paperback, hardcover, and audio format back to a single canonical record so your database stays clean.
Know exactly how well a book is documented before you rely on its data. The get_book_coverage tool returns a clear score so you can filter out poorly cataloged titles.
Skip the messy ID translation step. You just ask for a book, and the what_work tool instantly resolves it to the exact internal ID needed for deeper queries.
Get real community sentiment without scraping review sites. The get_work tool pulls member counts, review totals, and user tags directly from the LibraryThing database.
Eliminate the boilerplate of building HTTP clients. You connect this MCP once, and your agent handles all the API calls and JSON parsing automatically.
See it in action
Fixing duplicate book records
A user submits an ISBN for a French paperback, but your system already has the English hardcover. You use thing_isbn to find all variations, then use what_work to prove they share the same canonical ID and merge the records.
Filtering out bad data for a recommendation engine
You need high-quality metadata for a new feature. You run a batch of titles through get_book_coverage and drop anything with a score below 0.8, ensuring your model only trains on well-documented books.
Building a reading list app
A user asks for details on a specific sci-fi novel. Your agent uses what_work to get the ID, then calls get_work to pull the author, publication year, and community tags to display on the user's dashboard.
Auditing a digital library catalog
A librarian notices missing metadata for a collection of indie books. They use get_book_coverage to identify which titles lack community documentation and flag them for manual review.
The honest tradeoffs
Calling get_work with an ISBN
You pass an ISBN directly to get_work and get an error because it expects an internal work ID.
Always run what_work first to translate the ISBN into the correct ID, then pass that ID to get_work.
Ignoring the coverage score
You pull metadata for a brand new release and wonder why the review count is zero.
Check get_book_coverage first. If the score is low, the book is barely in the system, so missing data is expected.
Treating ISBNs as unique books
You use thing_isbn to fetch a list of IDs and assume each one is a completely different book.
Understand that this tool groups formats. Use what_work on those ISBNs to see which ones actually point to the same underlying title.
When It Fits, When It Doesn't
Use this if you need to map messy, real-world book editions to clean canonical records. The thing_isbn and what_work tools are built exactly for that. It is also the right choice if you need community-driven metadata like user tags and review counts via get_work. Do not use this if you just need to check if a book is currently in stock at a retail store. This is a bibliographic database, not an inventory system. If you need point-of-sale data or real-time pricing, look for an e-commerce or retail inventory MCP instead. Also, skip this if you only care about the text of the book itself. This gives you metadata about the book, not the content inside it.
Questions you might have
How do I use the LibraryThing MCP get_work tool? +
You first need the internal work ID. Use the what_work tool to translate your book query into an ID, then pass that ID to get_work to pull the full metadata.
Does the LibraryThing MCP thing_isbn tool require an API key? +
Yes, you need to register for a LibraryThing Developer Key to use the MCP. Once you add that key to your client configuration, tools like thing_isbn will work without extra setup.
What does the LibraryThing MCP get_book_coverage score mean? +
It is a zero-to-one rating showing how completely the community has cataloged a book. A score near one means the title has extensive metadata, while a low score means it is barely documented.
Can the LibraryThing MCP what_work tool find audiobooks? +
Yes. It resolves the canonical work ID for a title regardless of the format. Once you have that ID, you can use thing_isbn to find the specific ISBNs for the audio, paperback, and hardcover editions.
How many tools are in the LibraryThing MCP? +
There are four tools. You get what_work to find IDs, get_work for detailed metadata, thing_isbn to map editions, and get_book_coverage to check data quality.
How does the LibraryThing MCP thing_isbn tool handle international editions? +
It returns all ISBNs for a specific title across different regions. This includes paperback, hardcover, and localized print runs so your agent can map global inventory.
What happens if the LibraryThing MCP what_work tool cannot find a matching book? +
It returns a null identifier. Your AI client should handle this by prompting you for an ISBN or alternate title spelling before making another request.
Can I use the LibraryThing MCP get_work tool without a work ID? +
No. You must pass a valid work ID to get detailed metadata. Run the what_work tool first to resolve a title or ISBN into the required numeric identifier.
What information can I get from an ISBN lookup? +
An ISBN lookup returns the book title, author(s), publisher, publication date, page count, language, community ratings, and tags — all from the LibraryThing database.
We've already built the connector for LibraryThing. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 4 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.