digibib
Click on "Deploy 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., "@digibib list the volumes in my Digitale Bibliothek library"
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.
digibib5-mcp
A clone-in-progress of the Digitale Bibliothek 5 reader (Directmedia /
Digitale Bibliothek), built on a from-scratch reverse-engineering of its .DKI
volume format. It reads the original CD-ROM images - volume list, table of
contents, and decoded text - and exposes them over MCP and REST, with a
reader webapp.
The .DKI format was reversed from the real discs (see
reversing-mcp docs/DIGIBIB5_DKI_FORMAT.md).
Two format generations are supported: older single-table volumes (DB008) and
newer ones (DB074, DB006) with magic-prefixed TEXT.DKI, direct TREE.DKA
mapping, high-bit word lengths and .xml source markers.
Digibib5 itself is the oracle: run it alongside to compare rendered output.
Documentation
Doc | What |
setup, MCP config | |
first-timer guide: discs, costs (none), sanity check | |
env vars, ports, per-volume file layout | |
MCP ops, REST endpoints, Python library | |
repo layout, gates, codec map, release | |
symptoms and fixes |
Related MCP server: mcp-hathitrust
Status
Early. What works today:
Volume discovery - scans the install root and lists every CD-ROM image.
Descriptor - reads
DIGIBIB.TXTidentity (title etc.).TOC - parses
TREE.DKI(indented-text tree) into a nested table of contents.Text decode - decodes
TEXT.DKIrecords (tokenized word-stream codec, v2: flowing paragraphs, heads dropped, de-hyphenated).Search - FTS5 sidecar over decoded text with chapter snippets (
searchop, REST/api/.../search, reader search box).Figures -
IMAGES\BMP scans served over REST with per-chapter figure strips in the reader (imagesop,/api/.../images,/api/.../image/...).REST API + reader webapp - a Starlette backend serves the library as JSON, and a React/Vite/Tailwind reader renders the volume picker, TOC tree, and text.
Known v1 / approximate (tracked, to refine against the Digibib5 oracle):
The text codec's exact control-opcode grammar (heading levels, italics, links). Paragraph structure, running-head removal, de-hyphenation, spaced dashes, literal spans and reflowed line breaks are mapped (v2); output is flowing text but not yet byte-faithful.
Images (
IMAGES\*.BMP/images.lib) and the search indexes (INDEX.*/LINKS.*) are not wired up yet.
Solved 2026-10-26: the TREE.DKA node -> record mapping. The table is a
1-based start-record run for every node but the volume root (root starts at
record 0), located by monotonic-run scan. Clicking a TOC entry now renders the
whole chapter (all records until the next non-descendant node, capped at 100);
node_text reports record / record_end / records_total / truncated.
Format, in brief
A volume is a data\ folder:
File | Role |
| INI descriptor (identity shown in the CD picker) |
| TOC as indented CP1252 text (leading spaces = depth) |
| u32 node -> record table (1-based run for all nodes but the root; see CONFIGURATION) |
|
|
| search / cross-reference indexes (later) |
| page images at 4 zoom levels (later) |
MCP tool
One portmanteau, digibib:
digibib(operation="list_volumes")
digibib(operation="descriptor", volume_id="DB008")
digibib(operation="toc", volume_id="DB008", max_depth=3)
digibib(operation="node_text", volume_id="DB008", node_index=5)
digibib(operation="record_text", volume_id="DB008", record_index=0)
digibib(operation="search", volume_id="DB008", query="Nathanael", limit=10)
digibib(operation="images", volume_id="DB008", level=1)node_text returns the node's full chapter extent (record..record_end,
records_total, truncated when capped at 100 records) plus images
(figure names referenced by the chapter) and image_levels; record_text
reads one raw TEXT.DKI record; search returns FTS5 hits with the
containing chapter and a «»-marked snippet per hit.
The install root defaults to K:\Digitale Bibliothek\Bibliothek (override with
the DIGIBIB_ROOT env var or the root argument).
Library
from digibib5_mcp.dki import DigibibLibrary
lib = DigibibLibrary()
for ref in lib.list_volumes():
print(ref.id, ref.title)
vol = lib.open("DB008")
print(vol.title) # Digitale Bibliothek Band 8: Hoffmann
for root in vol.toc_tree():
print(root.title) # Hoffmann -> ...
print(vol.record_text(0)) # decoded record textRun
uv run digibib5-mcp # stdio MCP server
just api # REST backend only (Starlette on 14115)
just webapp # backend + Vite reader on http://127.0.0.1:14114just webapp runs web_sota/start.ps1: it starts the backend, bun installs
the frontend on first run, then launches the Vite dev server. The frontend
proxies /api to the backend.
Reader webapp
web_sota/ - React 18 + Vite 6 + Tailwind 4 + react-router + Zustand (Bun). AppLayout shell
(sidebar, topbar, health dot) with routed pages: Dashboard (library KPIs + onboarding),
Reader (volume picker, TOC tree, content pane, search, figures), Tools (live op harness),
Chat (local/cloud LLM, resident-first), Settings (backend + AI), Logs, Help. Ports:
14114 (frontend) / 14115 (backend REST).
Packaging
Fleet-standard: justfile (run / lint / test / release recipes), mcpb.json +
manifest.json for MCPB bundling (just pack), and scripts/release.ps1 for
the triple-play release (mcpb + NSIS installer + GitHub release).
Stack
Python 3.12+, FastMCP 3.2+, Pydantic v2, Starlette, uv. Frontend: React 18, Vite 6, Tailwind 4, Bun.
Legal
For reading Digitale Bibliothek volumes you own. Intended for interoperability, preservation, and access on modern systems.
Interoperability note (not legal advice). This project contains no
copy-protection circumvention and redistributes no content from the discs:
no texts, no images, no audio, no keys - only code that reads CD-ROMs you
own. The .DKI container is an undocumented but unprotected format; nothing
here defeats an effective technical protection measure. Reverse-engineering
a file format to make lawfully acquired data usable on current systems is
the interoperability case the EU Software Directive (Art. 6) expressly
permits. "Digitale Bibliothek" is named only to describe compatibility.
If you are unsure in your jurisdiction, ask a lawyer before redistributing
anything beyond the code.
Available Tools
1 tooldigibibA
DIGIBIB - read Digitale Bibliothek 5 volumes.
Operations:
list_volumes-> every installed CD-ROM volume: {id, title}.descriptor-> the volume's DIGIBIB.TXT identity keys.toc-> the table of contents as a nested tree (node index + record index per node). Use max_depth to trim.node_text-> decoded text for a TOC node: the full chapter extent (record..record_end, records_total, truncated flag).record_text-> decoded text for a raw TEXT.DKI record index.search-> full-text search over decoded text (needs query): [{record, node_index, chapter, snippet}]. First search per volume builds an FTS cache (~10 s), then instant.images-> figures at a zoom level (needs level or takes the highest): {levels, level, images: [{name, width, height, bpp, bytes, url}]}. Binary via the REST image endpoint (see url per figure).
NOTE: text decode is v2 (flowing paragraphs, heads dropped); output is readable but not yet byte-faithful.
Inputs: root, level, limit, query, +5 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
The single dispatcher tool exposes clearly separated operations (list_volumes, descriptor, toc, node_text, record_text, search, images) with distinct inputs and outputs. The only real overlap is node_text vs record_text, which both return decoded text and differ only by addressing scheme (TOC node vs raw TEXT.DKI record index) — the descriptions clarify this, but an agent could still pick the wrong one.
The operations inside the tool consistently follow a snake_case verb_noun pattern (list_volumes, node_text, record_text). The tool itself is a single server-named dispatcher ('digibib') rather than a verb_noun action, which is a minor deviation but acceptable for a multi-operation facade.
A single exposed tool would normally feel thin, but it packs seven substantive operations covering the whole read lifecycle, so the surface is larger than the count suggests. Still, the single-tool dispatch pattern makes discovery and selection harder than a small set of explicit tools would.
For a read-only CD-ROM library reader the coverage is strong: volume listing, metadata, TOC navigation, chapter/record extraction, full-text search, and figure retrieval. Gaps are minor — no cross-volume aggregated search and no export/citation output, but agents can work around both by iterating volumes.
Maintenance
Related MCP Connectors
MCP server for Project Gutenberg: 78,000+ public-domain ebooks with full plain-text retrieval.
Multi-engine scholarly research server for search, traversal, full text, and reading lists.
MCP server for Open Archives: Dutch genealogical records and historical page transcriptions.
Bible corpus MCP server: scripture, Greek/Hebrew interlinear data, cross-refs, semantic search.
Related MCP Servers
- AlicenseAqualityBmaintenanceThis MCP server enables AI agents to search and retrieve exact, cited passages from a large corpus of public-domain books, including full-text search, book metadata, chapters, quotes, and 'ask book' Q&A. Payments are handled via x402 micropayments on Base.8536 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to look up digitized-book holdings and catalog records by standard identifiers, retrieve bibliographic metadata, and check whether readable full-view copies are available.93 npmMIT
- AlicenseAqualityBmaintenanceThis read-only MCP server gives agents semantic search over an OpenViking knowledge base, plus tools to read a document's full text by URI and browse directories with their generated abstracts. It exposes no write operations, so lookups are all an agent can do.332 npmMIT
- AlicenseAqualityBmaintenanceThis server allows Large Language Models to consume S1000D data and publication modules as structured information instead of raw XML. It enables reading the content's hierarchy, applicability to specific products, and document verification status.6338 npmMIT