gutenberg-mcp-server
Server Details
MCP server for Project Gutenberg — 75,000+ public-domain ebooks with full plain-text retrieval.
- Status
- Healthy
- Uptime
- 100.0% over 41 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- cyanheads/gutenberg-mcp-server
- GitHub Stars
- 3
- Server Listing
- gutenberg-mcp-server
TDQS
Scored across 4 tools
Each tool targets a distinct function: browsing popular books, searching the catalog, fetching metadata, and retrieving text. No two tools overlap in purpose, and the descriptions make the boundaries clear.
All tools follow a consistent gutenberg_verb_noun pattern with snake_case naming. The two get_ verbs are differentiated by their objects (book vs text), and browse_popular/search_books are clearly distinct actions.
Four tools is a well-scoped count for a specialized Gutenberg server. Each tool serves a necessary step in the discovery-to-content workflow without redundancy.
The server covers the full read-only lifecycle: discovery (browse/search), metadata retrieval (get_book), and content retrieval (get_text). The metadata tool includes format URLs, and the text tool handles pagination, making the surface complete for its domain.
Available Tools
4 toolsgutenberg_browse_popularBrowse Popular Gutenberg BooksARead-onlyIdempotentInspect
Browse the most-downloaded Project Gutenberg books, ordered by popularity. Returns up to 32 titles with their Gutenberg IDs, authors, languages, and download counts. Optionally filter by language or topic. Use this as a discovery entry point — "what are the most popular classics in French?" — or as a heartbeat check that the catalog is reachable.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of books to return (1–32). Default 20 gives a useful overview without overwhelming context. | |
| topic | No | Filter by a subject or bookshelf keyword (case-insensitive phrase match). Example: "science fiction", "adventure", "detective". Applies on top of the language filter. | |
| languages | No | Restrict to books in these languages (two-character ISO 639-1 codes). Example: ["en"] for English only, ["de", "fr"] for German or French. Omit for all languages. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The limit that was applied. |
| books | No | Top books by download count, most popular first. |
| error | No | Present when the call failed. Absent on success. |
| shown | No | Number of books returned in this response. |
| truncated | No | True when the catalog held more matches than were returned. |
| totalInCatalog | No | Total books matching the filter in the full catalog (useful for context — "top 20 of 60,000"). |
| truncationCeiling | No | Download count of the least-popular book shown — omitted books have at most this many downloads. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only, idempotent, and open-world. The description adds useful behavioral context: it returns up to 32 titles with Gutenberg IDs, authors, languages, and download counts, and that filtering is optional. It does not disclose much beyond this, but the annotations cover the main safety profile.
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?
Two front-loaded sentences deliver the action, result scope, ordering, filters, and canonical use cases with no repetition or filler. Every sentence earns its place.
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?
For a read-only tool with no required parameters and an output schema, this description gives enough information to select and call it correctly. It could be slightly stronger by explicitly naming gutenberg_search_books for targeted queries, but the discovery framing already separates it from siblings.
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 coverage is 100%, with detailed per-parameter descriptions including defaults, examples, and match semantics. The free-text description only says 'Optionally filter by language or topic,' so it does not materially add meaning beyond what the schema already provides.
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 opens with a specific verb and resource: browse the most-downloaded Project Gutenberg books, ordered by popularity. It names the returned fields and frames the tool as a discovery entry point, clearly distinguishing it from the sibling search/get tools.
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 explicitly positions this as a discovery entry point and a heartbeat check, with an example question like 'what are the most popular classics in French?'. It does not explicitly name sibling alternatives or state when not to use it, so it lacks full exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
gutenberg_get_bookGet Gutenberg BookARead-onlyIdempotentInspect
Fetch complete metadata for a Project Gutenberg book by ID — title, authors (with birth/death years), translators, editors, subjects, bookshelves, languages, copyright status, and the full formats map with download URLs for each available format (plain text, HTML, EPUB, cover image, etc.). Use this before gutenberg_get_text to confirm a plain-text format is available and to get the direct download URL.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Project Gutenberg book ID. Visible in Gutenberg URLs (e.g., gutenberg.org/ebooks/1342) and returned by gutenberg_search_books and gutenberg_browse_popular. Example: 1342 for Pride and Prejudice, 2600 for War and Peace. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | No | Gutenberg ID. |
| error | No | Present when the call failed. Absent on success. |
| title | No | Book title. |
| authors | No | Primary author(s). |
| editors | No | Editors, if any. |
| formats | No | Map of MIME type to download URL. Key types: "text/plain; charset=utf-8" (preferred for gutenberg_get_text), "text/html", "application/epub+zip", "image/jpeg" (cover). Not every format is present for every book. |
| summary | No | First entry of summaries — the primary auto-generated summary of the work, or null when Gutendex has none. |
| subjects | No | Library of Congress subject headings. |
| copyright | No | Copyright status: false = public domain in the USA, true = under copyright, null = unknown. |
| languages | No | Two-character language codes for this edition. |
| summaries | No | Every summary Gutendex holds for this work, in upstream order. Usually one; some records carry a long and a short variant. Empty when there are none. |
| media_type | No | "Text" for readable books, "Sound" for audio books. Only "Text" books have plain-text content available for gutenberg_get_text. |
| bookshelves | No | Project Gutenberg bookshelf categories (e.g., "Best Books Ever Listings", "Category: Classics of Literature"). |
| translators | No | Translators, if this is a translated work. |
| download_count | No | Total downloads — popularity signal. |
| has_plain_text | No | True if media_type is "Text" AND a UTF-8 text/plain format ("text/plain; charset=utf-8") is present in formats — prerequisite for gutenberg_get_text. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds value by specifying the exact contents of the returned metadata (title, authors, formats map, etc.) and the practical purpose of retrieving the download URL, going beyond the annotation baseline.
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?
Two sentences, front-loaded with the core action and contents, followed by a precise usage directive. No wasted words; every clause earns its place.
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?
For a simple metadata-fetch tool with a full output schema and safety annotations, the description covers the essential use case and next step. Nothing an agent needs to call it correctly is missing.
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 schema description covers 100% of the single parameter (id) with source guidance and examples. The tool description adds no new parameter information, so the baseline 3 for high schema coverage applies.
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 'Fetch' and the resource 'complete metadata for a Project Gutenberg book by ID', enumerating specific metadata fields. It distinguishes itself from siblings by naming gutenberg_get_text and explaining the intended sequencing.
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?
Explicitly directs the agent to use this tool before gutenberg_get_text to confirm plain-text availability and obtain the download URL. This names an alternative and gives a concrete condition, leaving no ambiguity about when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
gutenberg_get_textGet Gutenberg Book TextARead-onlyIdempotentInspect
Retrieve the plain-text content of a Project Gutenberg book, stripped of the standard license header and footer so the response contains only the literary work. For long works — novels routinely run 500KB–2MB — use offset and limit to read in chunks rather than fetching the whole book at once. The response reports totalChars and remainingChars for reliable pagination. Prefers UTF-8 plain text; falls back to an HTML edition converted to text; refuses audio books (media_type "Sound") with a clear error.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Project Gutenberg book ID. Use gutenberg_search_books or gutenberg_get_book to find IDs. Example: 1342 for Pride and Prejudice, 2600 for War and Peace, 84 for Frankenstein. | |
| limit | No | Maximum number of characters to return in this chunk. Default 20,000 (~4–5 pages of prose). Increase toward 50,000 for large context windows. The actual returned length may be slightly less than limit when a natural paragraph boundary is found within 500 characters of the limit — check the length field in the response for the actual character count returned. | |
| offset | No | Character offset into the stripped literary text at which to start reading. 0 returns the beginning of the work. To read subsequent chunks, use offset = prior_offset + prior_length (the length field from the previous response — NOT offset + limit, because the actual returned length may be slightly less than limit due to paragraph-boundary trimming). |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | No | Gutenberg book ID. |
| text | No | The requested chunk of literary text, stripped of Gutenberg license boilerplate. Encoding: UTF-8. Line endings: normalized to LF. |
| error | No | Present when the call failed. Absent on success. |
| title | No | Book title, from the catalog record. |
| length | No | Number of characters in this chunk. |
| offset | No | Character offset where this chunk begins. |
| hasMore | No | True if there is more text after this chunk. When true, call again with offset = offset + length. |
| provenance | No | One-line source note with Project Gutenberg ID, title, and license URL. |
| totalChars | No | Total characters in the stripped literary text. Use with offset and length to determine progress and plan subsequent calls. |
| sourceFormat | No | The format that was fetched. "text/html" indicates HTML-to-text conversion was applied because no plain-text format was available. |
| remainingChars | No | Characters remaining after this chunk (totalChars - offset - length). 0 means this chunk includes the end of the book. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnly, openWorld, and idempotent hints, and the description adds substantial behavioral detail beyond that: stripping headers/footers, preferring UTF-8 plain text and falling back to HTML conversion, refusing audio books, and reporting totalChars/remainingChars for pagination. This is consistent with annotations and enriches the agent's understanding.
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 concise relative to the complexity, with each sentence carrying key information. It front-loads the core purpose, then provides practical usage details for chunking and pagination, and ends with fallback behaviors. There is no wasted wording; every sentence earns its place.
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 (only one required parameter) and the rich annotations and output schema, the description covers all necessary context: purpose, pagination mechanics, response fields, fallback behavior, and error cases. It is complete enough for an agent to call the tool correctly without further clarification.
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 schema already covers 100% of parameters, and the description adds significant semantics, especially for offset: it explicitly states to use prior_offset + prior_length rather than offset + limit due to paragraph-boundary trimming, and explains the limit default and actual return length behavior. This goes well beyond the schema's descriptions.
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 'Retrieve' and the resource 'plain-text content of a Project Gutenberg book', and specifies the key distinguishing detail of stripping license headers/footers. It also differentiates from siblings by naming that book IDs come from gutenberg_search_books or gutenberg_get_book, making the purpose unambiguous.
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 gives explicit guidance on when to use offset/limit for long works, explains pagination using totalChars/remainingChars, and notes it refuses audio books. It implies that for searching or getting book metadata, other tools should be used, effectively distinguishing this tool's usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
gutenberg_search_booksSearch Gutenberg BooksARead-onlyIdempotentInspect
Search the Project Gutenberg catalog of 78,000+ public-domain books. Matches title and author name with query words; filters by topic (subject or bookshelf keyword), language, author lifespan, or a specific list of Gutenberg IDs. Results are ordered by popularity (download count) by default. Returns book ID, title, authors, languages, subjects, and download count — use gutenberg_get_book for the full formats map before fetching text.
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | Narrow results to specific Gutenberg ID numbers. Other filters still apply. Useful for batch pre-fetching known IDs; use gutenberg_get_book for single-ID lookups. | |
| page | No | Page number for paginated results (1-indexed). Each page returns up to 32 books. Use totalCount to determine total pages. | |
| sort | No | Result ordering. "popular" (default) sorts by download count descending. "ascending" and "descending" sort by Gutenberg ID number. | popular |
| query | No | Words to match against book titles and author names (case-insensitive, space-separated). Example: "dickens expectations" matches Great Expectations by Charles Dickens. | |
| topic | No | Case-insensitive phrase to match against subjects and bookshelves. Example: "detective" returns books on the "Detective and Mystery Stories" bookshelf. Separate from query — topic searches categorization metadata, not title/author. | |
| languages | No | Filter to books in any of these two-character ISO 639-1 language codes. Example: ["en"] for English, ["fr", "de"] for French or German. | |
| author_year_end | No | Include only books with at least one author alive on or before this year. Example: author_year_start=1800 with author_year_end=1899 returns books with 19th-century authors. | |
| author_year_start | No | Include only books with at least one author alive on or after this year (positive = CE, negative = BCE). Combine with author_year_end for a range. |
Output Schema
| Name | Required | Description |
|---|---|---|
| page | No | Current page number. |
| books | No | Matching books, ordered by the sort parameter. |
| error | No | Present when the call failed. Absent on success. |
| hasMore | No | True if there are additional pages of results. |
| totalCount | No | Total number of books matching the query across all pages. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, lowering the bar. The description adds meaningful behavior beyond those: result ordering by popularity, the matching semantics over title/author, and the library scope (78,000+ public-domain books). It does not discuss pagination, but the schema's page parameter handles that.
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?
Two sentences, no filler, and the main search capability is front-loaded. Every clause adds useful information: scope, matching behavior, filters, ordering, return fields, and the pointer to gutenberg_get_book.
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 8 optional parameters, 100% schema coverage, read-only annotations, and an output schema, the description needs only to convey routing and high-level behavior. It does so completely, including the important downstream instruction to use gutenberg_get_book before fetching text.
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 100%, so the baseline is 3. The description adds value beyond the schema by grouping parameters into meaningful categories (topic, language, author lifespan, IDs) and clarifying the separation between query and topic. It also highlights the default sort behavior, which aids correct tool invocation.
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?
States a specific verb and resource: search the Project Gutenberg catalog, with explicit matching criteria (title/author, topic, language, author lifespan, IDs) and output fields. It distinguishes itself by naming gutenberg_get_book for the next step, and the broad search scope separates it from sibling browse/get tools.
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?
Clearly frames when to use this tool: when searching the catalog with filters. It explicitly routes the agent to gutenberg_get_book for the full formats map before fetching text, and the ids parameter schema reinforces that single-ID lookups should use gutenberg_get_book. It does not explicitly contrast with gutenberg_browse_popular, though the intent is reasonably inferable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- Changed
gutenberg_browse_popular4 fields changed- removed
Output schema / properties / books / items / properties / authors / items / properties / birth_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / books / items / properties / authors / items / properties / birth_year / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / books / items / properties / authors / items / properties / death_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / books / items / properties / authors / items / properties / death_year / typeAdded value: +[ + "number", + "null" +]
- Changed
gutenberg_get_book16 fields changed- removed
Output schema / properties / authors / items / properties / birth_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / authors / items / properties / birth_year / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / authors / items / properties / death_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / authors / items / properties / death_year / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / copyright / anyOfRemoved value: -[ - { - "type": "boolean" - }, - { - "type": "null" - } -] - added
Output schema / properties / copyright / typeAdded value: +[ + "boolean", + "null" +] - removed
Output schema / properties / editors / items / properties / birth_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / editors / items / properties / birth_year / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / editors / items / properties / death_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / editors / items / properties / death_year / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / summary / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / summary / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / translators / items / properties / birth_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / translators / items / properties / birth_year / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / translators / items / properties / death_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / translators / items / properties / death_year / typeAdded value: +[ + "number", + "null" +]
- Changed
gutenberg_search_books4 fields changed- removed
Output schema / properties / books / items / properties / authors / items / properties / birth_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / books / items / properties / authors / items / properties / birth_year / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / books / items / properties / authors / items / properties / death_year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / books / items / properties / authors / items / properties / death_year / typeAdded value: +[ + "number", + "null" +]
4 tool updates
- Changed
gutenberg_browse_popular2 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `no_results`: No books match the language/topic filter combination. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `no_results`: No books match the language/topic filter combination. `catalog_unavailable`: The Project Gutenberg catalog did not answer within the time this server allows for one browse. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "no_results" -]New value: +[ + "no_results", + "catalog_unavailable" +]
- Changed
gutenberg_get_book5 fields changed- changed
Output schema / anyOfPrevious value: -[ - { - "not": { - "required": [ - "error" - ] - }, - "required": [ - "id", - "title", - "authors", - "translators", - "editors", - "subjects", - "bookshelves", - "languages", - "copyright", - "media_type", - "download_count", - "summary", - "formats", - "has_plain_text" - ] - }, - { - "required": [ - "error" - ] - } -]New value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "id", + "title", + "authors", + "translators", + "editors", + "subjects", + "bookshelves", + "languages", + "copyright", + "media_type", + "download_count", + "summary", + "summaries", + "formats", + "has_plain_text" + ] + }, + { + "required": [ + "error" + ] + } +] - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `catalog_unavailable`: The Project Gutenberg catalog did not answer within the time this server allows for one lookup. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "not_found" -]New value: +[ + "not_found", + "catalog_unavailable" +] - added
Output schema / properties / summariesAdded value: +{ + "description": "Every summary Gutendex holds for this work, in upstream order. Usually one; some records carry a long and a short variant. Empty when there are none.", + "items": { + "type": "string" + }, + "type": "array" +} - changed
Output schema / properties / summary / descriptionPrevious value: -"Auto-generated summary of the work, when available. Absent on many older records."New value: +"First entry of summaries — the primary auto-generated summary of the work, or null when Gutendex has none."
- Changed
gutenberg_get_text2 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `audio_book`: The book is an audio recording (media_type \"Sound\"), not a text book — no literary plain text is available. `no_text_format`: The book has no UTF-8 plain-text or HTML edition available to read (for example an older ASCII-only entry). `offset_out_of_range`: The offset is greater than or equal to totalChars (past the end of the book). `text_fetch_failed`: The Gutenberg file server returned an error or did not respond within the timeout. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `audio_book`: The book is an audio recording (media_type \"Sound\"), not a text book — no literary plain text is available. `no_text_format`: The book has no UTF-8 plain-text or HTML edition available to read (for example an older ASCII-only entry). `offset_out_of_range`: The offset is greater than or equal to totalChars (past the end of the book). `text_fetch_failed`: The Gutenberg file server returned an error or did not respond within the timeout. `catalog_unavailable`: The catalog lookup that precedes reading a book did not answer within the time this server allows. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "not_found", - "audio_book", - "no_text_format", - "offset_out_of_range", - "text_fetch_failed" -]New value: +[ + "not_found", + "audio_book", + "no_text_format", + "offset_out_of_range", + "text_fetch_failed", + "catalog_unavailable" +]
- Changed
gutenberg_search_books2 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `no_results`: The query matched no books in the catalog. `page_out_of_range`: The requested page number is past the last page of results for this query. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `no_results`: The query matched no books in the catalog. `page_out_of_range`: The requested page number is past the last page of results for this query. `catalog_unavailable`: The Project Gutenberg catalog did not answer within the time this server allows for one search. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "no_results", - "page_out_of_range" -]New value: +[ + "no_results", + "page_out_of_range", + "catalog_unavailable" +]
4 tool updates
- Changed
gutenberg_browse_popular6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "books", + "totalInCatalog", + "truncated", + "shown", + "cap" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `no_results`: No books match the language/topic filter combination. Other values are possible when a failure originates below the handler.", + "examples": [ + "no_results" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "books", - "totalInCatalog", - "truncated", - "shown", - "cap" -]
- Changed
gutenberg_get_book6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "id", + "title", + "authors", + "translators", + "editors", + "subjects", + "bookshelves", + "languages", + "copyright", + "media_type", + "download_count", + "summary", + "formats", + "has_plain_text" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "id", - "title", - "authors", - "translators", - "editors", - "subjects", - "bookshelves", - "languages", - "copyright", - "media_type", - "download_count", - "summary", - "formats", - "has_plain_text" -]
- Changed
gutenberg_get_text6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "id", + "title", + "text", + "offset", + "length", + "totalChars", + "remainingChars", + "hasMore", + "provenance", + "sourceFormat" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: No book exists with the given ID. `audio_book`: The book is an audio recording (media_type \"Sound\"), not a text book — no literary plain text is available. `no_text_format`: The book has no UTF-8 plain-text or HTML edition available to read (for example an older ASCII-only entry). `offset_out_of_range`: The offset is greater than or equal to totalChars (past the end of the book). `text_fetch_failed`: The Gutenberg file server returned an error or did not respond within the timeout. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "audio_book", + "no_text_format", + "offset_out_of_range", + "text_fetch_failed" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "id", - "title", - "text", - "offset", - "length", - "totalChars", - "remainingChars", - "hasMore", - "provenance", - "sourceFormat" -]
- Changed
gutenberg_search_books6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "books", + "totalCount", + "page", + "hasMore" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `no_results`: The query matched no books in the catalog. `page_out_of_range`: The requested page number is past the last page of results for this query. Other values are possible when a failure originates below the handler.", + "examples": [ + "no_results", + "page_out_of_range" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "books", - "totalCount", - "page", - "hasMore" -]
3 tool updates
- Changed
gutenberg_browse_popular1 field changed- changed
Output schema / properties / books / items / properties / has_plain_text / descriptionPrevious value: -"True if media_type is \"Text\" AND a text/plain format is available via gutenberg_get_text."New value: +"True if media_type is \"Text\" AND a UTF-8 text/plain format is available via gutenberg_get_text."
- Changed
gutenberg_get_book1 field changed- changed
Output schema / properties / has_plain_text / descriptionPrevious value: -"True if media_type is \"Text\" AND a text/plain format (UTF-8 or ASCII) is present in formats — prerequisite for gutenberg_get_text."New value: +"True if media_type is \"Text\" AND a UTF-8 text/plain format (\"text/plain; charset=utf-8\") is present in formats — prerequisite for gutenberg_get_text."
- Changed
gutenberg_search_books1 field changed- changed
Output schema / properties / books / items / properties / has_plain_text / descriptionPrevious value: -"True if the book has media_type \"Text\" AND a text/plain format available — prerequisite for gutenberg_get_text."New value: +"True if the book has media_type \"Text\" AND a UTF-8 text/plain format available — prerequisite for gutenberg_get_text."
4 tool updates
- First observed
gutenberg_browse_popular - First observed
gutenberg_get_book - First observed
gutenberg_get_text - First observed
gutenberg_search_books
Related MCP Connectors
Gutendex MCP — wraps Gutendex API for Project Gutenberg books (free, no auth)
Free, no-key Bible MCP server — 86 translations in 32 languages, from any MCP client.
MCP server for Russian books search, details, and recommendation candidates.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents access to the world's public domain library. Search, read, and navigate books and audiobooks from Project Gutenberg and LibriVox.-
- AlicenseNot gradedqualityDmaintenanceEnables reading books from Project Gutenberg via MCP, with tools to search books, fetch metadata and full text, and retrieve passages by fixed-size keys.MIT
- AlicenseNot gradedqualityDmaintenanceA well-documented MCP server that exposes a local SQLite catalog of public-domain books through tools like search, get, filter by genre, top-rated, and catalog stats.MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets an LLM browse, search, and download books from OPDS catalogs (e.g., Project Gutenberg, Standard Ebooks) using tools for feed navigation, full-text search, and acquisition link downloads.41AGPL 3.0
Glama MCP Gateway
Add one secure layer between your agents and this server.