LibraryThing MCP. Map book editions and check catalog coverage by ISBN.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
LibraryThing connects your AI client to a deep database of book metadata, works, and editions. Use it to look up books by ISBN, map out all known variations of an author's work across different formats (hardcover, audio, international), or check which libraries might own a title for interlibrary research.
What your AI agents can do
Get book coverage
Calculates and returns a single score (0-1) showing how thoroughly the book’s data is cataloged on LibraryThing.
Get work
Pulls detailed metadata for an entire work, including title, author list, member count, and review count, using its unique Work ID.
Thing isbn
Lists all known ISBNs for a single book across various formats like paperback, audio, or international editions.
You can pass any book's identifier and get its unique LibraryThing Work ID, which is required for nearly all other lookups.
It finds every known format (audiobook, hardcover, international) associated with a single work using ISBNs.
Retrieve comprehensive data on an entire body of work, including author count and community review metrics, using the Work ID.
The system returns a score (0-1) indicating how completely LibraryThing has cataloged the book's details.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
LibraryThing MCP Server: 4 Tools for Bibliographic Data
These four tools let you find a work's unique ID, map every edition it has, get full author metadata, and check its data completeness score.
019d8452get book coverage
Calculates and returns a single score (0-1) showing how thoroughly the book’s data is cataloged on LibraryThing.
019d8452get work
Pulls detailed metadata for an entire work, including title, author list, member count, and review count, using its unique Work ID.
019d8452thing isbn
Lists all known ISBNs for a single book across various formats like paperback, audio, or international editions.
019d8452what work
Accepts an ISBN and returns the necessary LibraryThing Work ID needed to access other detailed data points.
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 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
LibraryThing connects your AI client directly to a deep database of book metadata and works. You're looking at an entire library system in one place. This server lets you look up books by ISBN, map out every single variation of an author’s work—like hardcover, paperback, or audiobooks—and check how well the data is cataloged.
The what_work tool takes any book's identifier and spits out its unique LibraryThing Work ID. You gotta have that ID for almost everything else you wanna do here.
Once you pull that Work ID, the get_work tool lets you retrieve detailed metadata about the entire body of work. It pulls things like the full title, a count of all associated authors, and how many community reviews the book has racked up.
If you need to map out every single format for one book—say, an ebook, a hardcover, or an international print run—you use the thing_isbn tool. Just passing in an ISBN lists all known formats tied to that core work.
To see how complete the record is, check the coverage score. The get_book_coverage tool gives you a single score between 0 and 1. This number tells you exactly how thoroughly LibraryThing has cataloged the book's details; a 1.0 means it’s fully covered in their system.
When your agent needs to work through this, the process is always sequential. First, you give it an ISBN and run what_work to get that necessary Work ID. Next, if you wanna know about all editions, you can use thing_isbn. If you want stats on the whole body of work, you feed that Work ID into get_work.
You might also call get_book_coverage right away just to see how much data is available for that title.
Think of it this way: you start with a random book identifier. The system uses what_work to find the internal ID, then gives you options—you can use thing_isbn to list every format, or you can pass that ID to get_work to pull all the community metrics and author lists. It's a solid workflow for researchers who need to track down obscure editions or just want to know if LibraryThing has enough data on a title to be useful.
How LibraryThing MCP Works
- 1 First, your agent runs
what_workusing an ISBN to get the primary Work ID for a given title. - 2 Next, it passes that Work ID into
get_workto pull all associated metadata like authors and ratings. - 3 Finally, you can use
thing_isbnorget_book_coverageto expand your data set by listing editions or checking catalog completeness.
The bottom line is: You establish the book's unique ID first, then pull the specific details and related editions in subsequent calls.
Who Is LibraryThing MCP For?
Academic researchers, librarians, or content developers who constantly cross-reference obscure titles are the primary users. If your job involves verifying metadata across multiple sources or tracking down a rare edition for an author, this server is built for you. Stop manually checking ISBN sites; let your agent do it.
Needs to track down the first published edition of a specific text or verify if multiple translations exist before writing a literature review.
Uses it to gather accurate metadata (author, publication year, community rating) for product documentation or educational content.
Needs to check the catalog coverage score (get_book_coverage) to see how complete a title's record is before recommending it to a patron.
What Changes When You Connect
- Stop guessing about a book's completeness. Run
get_book_coverageto get a precise score (0-1) showing how fully the title is tracked in the database. - Don't waste time on single formats. Use
thing_isbnonce, and it returns every known edition—audio, hardcover, international—for that same work. - Get reliable data points for deep analysis using
get_work. You pull author counts and community reviews without leaving the chat window. - No more manual ID searches. First, run
what_workwith an ISBN to immediately get the unique Work ID needed before calling any other tool. - The agent handles the complexity. Instead of calling four different APIs yourself, you just ask for 'all book data for X,' and your client runs the right sequence.
Real-World Use Cases
Writing a Comparative Study
A student needs to write about an author's global impact. They give their agent a core ISBN. The agent first uses what_work to find the ID, then runs thing_isbn to list every international and regional edition. Finally, it uses get_work to pull the total member count across all works.
Verifying Rare Book Availability
An archivist needs to know if a specific historical text was ever fully cataloged by LibraryThing. They use their agent to run get_book_coverage on the ISBN. The resulting score immediately tells them if they need to dig deeper into other archives.
Building Product Data Schemas
A developer needs a full data object for a book entry in their app. They use what_work to get the ID, then feed that ID into get_work and run thing_isbn. This gives them a structured payload containing metadata and all known editions.
Resolving Conflicting Metadata
A content team has an old book entry with incomplete data. They ask the agent to use get_book_coverage on the ISBN. If the score is low, they know the metadata is unreliable and need to source more information.
The Tradeoffs
Calling get_work first.
The user tries to pass an ISBN directly into get_work because they think it's a universal search field. The call fails or returns generic data because the tool requires a Work ID, not an ISBN.
→
You must run what_work with the ISBN first. This provides the mandatory Work ID that you then pass to get_work. It’s a two-step process.
Ignoring edition variations.
The user only looks up the main paperback ISBN and assumes they have all the data, missing information on the hardcover or audiobook versions.
→
Always run thing_isbn after finding the Work ID. This ensures your agent pulls metadata for every format that exists.
Stopping too early.
The user gets a list of editions from thing_isbn but never checks the coverage score. They assume because an ISBN exists, all data points are complete and reliable.
→
After mapping editions, check the get_book_coverage score. This metric tells you if the data is as complete as the editions listed.
When It Fits, When It Doesn't
Use this server when your goal is data modeling or exhaustive bibliographic research on a known title. You need to know: 1) The unique Work ID, 2) Every related ISBN/format, and 3) How complete the dataset is.
Don't use it if you are performing broad keyword searches (you’d need a general search API for that). This server is built on structured identifiers. If your problem is 'Find all books about quantum physics,' this won't help; you need a subject index tool. But if the problem is, 'I have ISBN X and I need every piece of metadata about it—editions included,' then this set of tools is exactly what you need.
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 server provides 4 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Trying to track down an obscure book's data feels like detective work.
Today, tracking a single title means jumping between three different sites: the main catalog for general info, Google Books for ISBN variations, and then maybe WorldCat just to check library holdings. You spend 20 minutes copy-pasting IDs, switching tabs, and cross-referencing conflicting data points.
With this MCP server, you ask your agent one question—'What is the full profile for this book?' Your agent runs `what_work` first, then uses that ID to run `get_book_coverage`, pulling all necessary IDs and metadata into a single, structured output. You get the answer without leaving the chat window.
LibraryThing MCP Server: Get complete book data in four simple steps.
Before this server, getting a full profile required manual execution of multiple lookup types. You had to find the Work ID separately from the ISBNs, then run one query for metadata and another just for coverage. It was slow, brittle, and prone to human error.
Now you build robust data pipelines right in your agent. The flow is predictable: Identify -> Map Editions (`thing_isbn`) -> Get Details (`get_work`) -> Verify Completeness (`get_book_coverage`). You're running a full bibliographic audit with one prompt.
Common Questions About LibraryThing MCP
How do I get the Work ID using LibraryThing MCP Server? +
Run the what_work tool. You feed it an ISBN, and it returns the necessary unique Work ID that you need for all other lookups.
Can I use get_book_coverage without a work ID? +
No. The coverage score requires a specific book identifier. Always run what_work first to establish the correct Work ID before checking coverage using get_book_coverage.
Which tool should I use for finding all formats of a book? +
thing_isbn is the right tool. It explicitly lists every known ISBN variation (audio, hardcover, etc.) associated with that core work.
Is get_work better than just searching by title? +
Yes. get_work uses a fixed ID and pulls structured data points like author counts and community ratings; it doesn't rely on free-text search, making the results much more reliable for your agent.
Does the LibraryThing MCP Server require an API key when running `get_book_coverage`? +
Nope, you don't need a key. The server is free and doesn't require any API credentials for basic calls like getting coverage scores. This makes initial testing straightforward.
Why must I use `what_work` before calling `get_work`? +
You need the Work ID first because it acts as a unique identifier for the entire body of work, not just one edition. what_work pulls that specific ID you then pass to get detailed info.
If I run `thing_isbn` and get zero results, what does this mean? +
It means the book doesn't have any other published editions (like audio or international versions) linked to that ISBN. It’s not an error; it just confirms no alternative formats were found.
What kind of data should I expect from `get_work` compared to other tools? +
Expect a full profile here—things like member count, review counts, and multiple metadata points. Other tools focus on narrow tasks; get_work gives you the comprehensive picture.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Open Food Facts Alternative
Access the world's largest open food database — retrieve nutrition facts, ingredients, and environmental scores for millions of products.
The Met Museum
Explore 470,000+ artworks from The Metropolitan Museum of Art — search by artist, title, culture, date and department.
BigOven
Access over a million recipes via BigOven — search dishes, read reviews, and explore collections directly from any AI agent.
You might also like
FreshBooks
Manage small business accounting via FreshBooks — track clients and invoices, handle payments and billing via AI agents.
Lancerkit
Connect Lancerkit to any AI agent via MCP.
USPS Developer Portal
Manage US mail — audit addresses, tracking, and ZIP codes via AI.