Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@LibraLM MCP Server summarize chapter 5 of 'Atomic Habits'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Access 50+ book summaries and chapter breakdowns directly in Claude Desktop through the Model Context Protocol (MCP).
LibraLM MCP Server brings a library of AI-generated book summaries to your Claude Desktop conversations. Search for books, read comprehensive summaries, explore chapter-by-chapter breakdowns, and get instant access to key insights from business, self-help, and educational books.
Related MCP server: Claude RAG MCP Pipeline
📚 50+ Book Summaries - Access a growing library of professionally summarized books
🔍 Smart Search - Find books by title, author, or ISBN
📖 Chapter Breakdowns - Get detailed summaries of individual chapters
📋 Table of Contents - View complete book structure with chapter descriptions
🎯 Key Insights - Extract main themes, frameworks, and actionable takeaways
🔐 Secure API - Protected access with API key authentication
To install libralm_mcp_server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @libralm-ai/libralm_mcp_server --client claudeClaude Desktop installed
Python 3.10 or higher
LibraLM API key (get one at libralm.com)
Clone the repository:
git clone https://github.com/libralm-ai/libralm_mcp_server.git
cd libralm_mcp_serverInstall dependencies:
pip install -r requirements.txtGet your API key:
Visit libralm.com
Sign in with Google or GitHub
Copy your API key from the dashboard
Configure Claude Desktop:
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"libralm": {
"command": "uvx",
"args": ["--from", "libralm-mcp-server", "libralm-mcp-server"],
"env": {
"LIBRALM_API_KEY": "your_api_key_here"
}
}
}
}Restart Claude Desktop
search_booksSearch for books by title, author, or ISBN.
Search for "Atomic Habits"
Find books by James Clear
Look up ISBN 0735211299get_book_infoGet detailed information about a specific book.
Get details for book ID 0735211299
Show me information about this bookget_book_summaryGet the comprehensive AI-generated summary of a book.
Summarize "Atomic Habits"
Give me the main points of this bookget_table_of_contentsView the complete chapter list with descriptions.
Show me the chapters in "Atomic Habits"
What topics does this book cover?get_chapter_summaryGet a detailed summary of a specific chapter.
Summarize chapter 3 of "Atomic Habits"
What's in the first chapter?Here are some example prompts you can use with Claude:
"Search LibraLM for books about habits"
"What books do you have on leadership?"
"Give me a summary of 'Outlive'"
"Show me chapter 5 of 'The Wealth Ladder'"
"Find books by Adam Grant"
LIBRALM_API_KEY (required): Your LibraLM API key
Free tier: 50 API calls per month
Pro tier: Unlimited API calls
Rate limiting: 10 requests per minute
Verify your API key is correct in the configuration
Check that you've copied the entire key including the prefix
Ensure you're using a valid book ID
The book may not be in the library yet
Check your internet connection
Verify the API endpoint is accessible
Ensure your API key has not exceeded its usage limit
We welcome contributions! Please see our Contributing Guide for details.
This project is licensed under the MIT License - see the LICENSE file for details.
📧 Email: support@libralm.com
🐛 Issues: GitHub Issues
LibraLM Web - Web dashboard and API key management
MCP Specification - Learn more about MCP
Built with ❤️ by the LibraLM team
Get detailed information about a specific book
| Name | Required | Description | Default |
|---|---|---|---|
| book_id | Yes |
| Name | Required | Description |
|---|---|---|
| tier | No | |
| title | Yes | |
| author | No | |
| length | No | |
| book_id | Yes | |
| summary | No | |
| category | No | |
| subtitle | No | |
| has_summary | Yes | |
| release_date | No | |
| has_chapter_summaries | Yes | |
| has_table_of_contents | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify aspects like authentication needs, rate limits, error handling, or what 'detailed information' entails beyond the schema. This leaves significant gaps in understanding the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (one parameter) and the presence of an output schema, the description is somewhat complete but lacks depth. It doesn't clarify the scope of 'detailed information' or how it differs from sibling tools, which could hinder the agent's ability to use it effectively in context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage, but the description adds minimal value by implying the parameter is for a 'specific book'. However, it doesn't explain the format or constraints of 'book_id' (e.g., whether it's an ISBN, internal ID, or something else). Since there's only one parameter, the baseline is 4, but the lack of semantic detail reduces it to 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific book'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'get_book_summary' or 'list_books', which limits its effectiveness in helping the agent choose between alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'get_book_summary' or 'list_books'. It implies usage for detailed book information but lacks explicit context, exclusions, or prerequisites, leaving the agent to infer when this is the appropriate choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the main summary for a book
| Name | Required | Description | Default |
|---|---|---|---|
| book_id | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' a summary, implying a read operation, but doesn't mention any behavioral traits like permissions needed, rate limits, error handling, or what the output contains. This leaves significant gaps for an agent to understand how to use it effectively.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no wasted words, making it highly efficient and easy to parse. It's appropriately sized for a simple tool and front-loaded with the core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (one parameter) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete behavioral context, it doesn't fully compensate for the lack of structured data, leaving gaps in usage understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description implies the parameter 'book_id' is used to identify a book for getting its summary, adding meaning beyond the schema's 0% coverage. Since there's only one parameter, the baseline is high, and the description adequately clarifies its purpose without needing detailed syntax.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('main summary for a book'), making it easy to understand what it does. However, it doesn't explicitly distinguish this tool from its sibling 'get_book_details', which might also provide summary information, so it misses full differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'get_book_details' or 'get_chapter_summary'. It lacks context about prerequisites, such as needing a book ID from 'list_books', or exclusions for when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the summary for a specific chapter of a book
| Name | Required | Description | Default |
|---|---|---|---|
| book_id | Yes | ||
| chapter_number | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get the summary' which implies a read-only operation, but doesn't mention any behavioral traits such as permissions needed, rate limits, error handling, or what the summary format includes. This is a significant gap for a tool with no annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without any waste. It's appropriately sized and front-loaded, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema (which handles return values), no annotations, and simple parameters, the description is minimally adequate but incomplete. It covers the basic purpose but lacks usage guidelines, parameter details, and behavioral context, making it insufficient for full understanding without external information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning the schema provides no descriptions for the two parameters. The description doesn't add any meaning beyond the parameter names (e.g., it doesn't explain what 'book_id' or 'chapter_number' represent, their formats, or constraints). With low coverage, the description fails to compensate, leaving parameters poorly documented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Get') and resource ('summary for a specific chapter of a book'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_book_summary' or 'get_table_of_contents', which might also provide chapter-related information, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'get_book_summary' or 'get_table_of_contents'. It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the table of contents for a book with chapter descriptions
| Name | Required | Description | Default |
|---|---|---|---|
| book_id | Yes |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't indicate whether this is a read-only operation, what permissions might be required, potential rate limits, or error conditions. While 'Get' implies a read operation, the lack of explicit safety or behavioral context leaves significant gaps for an agent to understand how to properly invoke this tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information. Every word earns its place, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no annotations, but with an output schema), the description is adequate but incomplete. The output schema likely handles return values, so the description doesn't need to explain those. However, for a tool with no annotations, it should provide more behavioral context (e.g., read-only nature, error handling) to be fully complete for agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description mentions 'for a book' which implies the book_id parameter, but with 0% schema description coverage and only one parameter, this adds minimal value beyond what's obvious from the schema. The baseline for a single parameter with low schema coverage would be higher, but since the description doesn't explain what format the book_id should be (e.g., ISBN, internal ID) or where to obtain it, it only partially compensates for the schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and resource ('table of contents for a book with chapter descriptions'), making the purpose immediately understandable. It distinguishes from siblings like 'get_book_details' or 'get_book_summary' by focusing specifically on the table of contents structure rather than general book information or individual chapters. However, it doesn't specify whether this includes only chapter titles or also page numbers, which keeps it from being a perfect 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'get_book_details' or 'list_books'. It doesn't mention prerequisites, such as needing a valid book_id from another operation, or clarify what context makes this tool preferable to siblings. The user must infer usage from the tool name alone, which is insufficient for optimal agent decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List all available books with their basic information
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states it lists books with basic information, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, pagination behavior, or what 'basic information' includes. For a tool with no annotation coverage, this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose ('List all available books') and adds necessary context ('with their basic information'). There is zero waste or redundancy, making it appropriately sized for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally complete. However, with no annotations and siblings present, it lacks guidance on usage context and behavioral details. The output schema handles return values, but the description could better address when to use this versus alternatives.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides, and it appropriately doesn't mention any parameters. Baseline for 0 parameters is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('List') and resource ('all available books') with the scope of 'basic information'. It distinguishes from siblings like get_book_details or get_book_summary by specifying it returns basic information for all books rather than detailed information for specific books. However, it doesn't explicitly contrast with all siblings (e.g., get_table_of_contents).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus the sibling tools. It doesn't mention alternatives like get_book_details for detailed information or get_book_summary for summaries, nor does it specify any prerequisites or contextual constraints for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0get_book_details1 field changedInput schema / titleAdded value: +"get_book_detailsArguments"get_book_summary1 field changedInput schema / titleAdded value: +"get_book_summaryArguments"get_chapter_summary1 field changedInput schema / titleAdded value: +"get_chapter_summaryArguments"get_table_of_contents1 field changedInput schema / titleAdded value: +"get_table_of_contentsArguments"list_books1 field changedInput schema / titleAdded value: +"list_booksArguments"get_book_detailsget_book_summaryget_chapter_summaryget_table_of_contentslist_booksEvery tool has a clearly distinct purpose with no ambiguity. 'get_book_details' provides comprehensive information, 'get_book_summary' focuses on the main summary, 'get_chapter_summary' targets specific chapters, 'get_table_of_contents' offers structural overview, and 'list_books' enumerates available books. The descriptions make it easy to distinguish between these related but non-overlapping functions.
All tools follow a consistent verb_noun pattern using snake_case throughout. The naming convention is perfectly uniform with 'get_' or 'list_' prefixes followed by specific resource identifiers, making the tool set highly predictable and readable for agents.
Five tools is well-scoped for a book/library management server, with each tool earning its place. This count provides comprehensive coverage for book exploration without being overwhelming or insufficient, falling within the ideal 3-15 tool range for focused domain coverage.
The tool surface provides excellent read-only coverage for book exploration, including listing, detailed views, summaries, and structural information. The only minor gap is the absence of write operations (create/update/delete books or chapters), but for a library/reading-focused server, this is reasonable and agents can work effectively with the provided retrieval tools.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.
Your professional network in Claude — search contacts, log notes, and send warm intros.
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
Real-time Claude & Anthropic news from your own Claude — free, no API key.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/libralm-ai/libralm_mcp_server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
