z3950-mcp
Install YAZ first —
brew install yaz(macOS) orapt-get install yaz(Debian/Ubuntu). Z39.50 is spoken byyaz-client, a system binary no installer can ship; the buttons install the server around it. Without YAZ the server still starts and every search returns an explicityaz-client not founderror.A desktop app does not inherit your shell's
PATH, so the server also looks in Homebrew's usual locations on its own. If YAZ lives somewhere unusual, pointYAZ_CLIENTat the binary (the Claude Desktop installer offers a field for it).
An MCP server that lets an AI assistant search library catalogs over Z39.50 and get back structured MARC 21 records.
It talks to catalogs through YAZ
(yaz-client) and parses the returned records with
pymarc, so you get clean, standards-based
bibliographic data — not scraped HTML.
Why
Most Polish (and international) library OPACs — Prolib/Integro, Virtua, Aleph, Alma, Koha — expose a Z39.50 server, the decades-old library-standard search protocol. It returns MARC 21, which is far more reliable to consume than scraping a web catalog. This server puts that behind two simple MCP tools.
Requirements
- Python ≥ 3.10
- The YAZ toolkit (
yaz-client):- macOS:
brew install yaz - Debian/Ubuntu:
apt-get install yaz
- macOS:
The binary is looked up on PATH first, then in /opt/homebrew/bin and
/usr/local/bin. Those two exist because a desktop MCP host — Claude Desktop,
Cursor — is launched from the GUI and inherits launchd's PATH
(/usr/bin:/bin:/usr/sbin:/sbin), which contains no Homebrew: without the
fallback, a correctly installed YAZ would still look missing.
Set YAZ_CLIENT to an absolute path to override the search entirely. A
value that is not executable is an error rather than a reason to keep looking —
otherwise a typo would surface much later as a confusing "not found".
Install
git clone https://github.com/mpasternak/z3950-mcp
cd z3950-mcp
uv sync
Tools
list_targets()
Lists the preconfigured catalogs — see Public Z39.50 resources
below. Each entry's key can be passed to search.
search(target, query, by="any", start=1, count=5, include_raw_marc=false)
Searches a catalog and returns parsed MARC records.
- target — a registry
keyabove, or an ad-hochost:port/databasestring. - by — index to search:
any,title,author,subject,isbn,issn,publisher,year,lccn,id, orpqfto passquerythrough as a raw PQF query. - count — how many records to return (max 50). Use
count=1with a narrow query (e.g. by ISBN) to fetch a single full record. - include_raw_marc — also include the full MARC record as text.
Example result for search("bn", "Pan Tadeusz", by="title", count=1):
{
"target": "bn-nl.alma.exlibrisgroup.com:1921/48OMNIS_NLOP",
"query": "@attr 1=4 \"Pan Tadeusz\"",
"hits": 1406,
"returned": 1,
"records": [
{
"control_number": "991000041299705066",
"title": "Pan Tadeusz czyli Ostatni zajazd na Litwie : historia szlachecka...",
"author": "Mickiewicz, Adam (1798-1855)",
"year": "1994",
"isbn": ["8370010938"],
"publisher": "\"Alfa-Wero\"",
"language": "pol",
"subjects": ["Poezja polska -- 19 w."]
}
]
}
Public Z39.50 resources
Catalogs below were verified reachable (2026-07) — they return live MARC 21.
Ones with a key are built in (search("bn", …)); the rest you pass as an
ad-hoc host:port/database.
Polish
| key | library | connection |
|---|---|---|
bn |
Biblioteka Narodowa | bn-nl.alma.exlibrisgroup.com:1921/48OMNIS_NLOP |
The National Library has the broadest Polish holdings. Most other Polish libraries expose Z39.50 only through the KaRo federation and don't publish their host/port openly — to find more:
- KaRo (Katalog Rozproszony Bibliotek Polskich) — https://karo.umk.pl, a YAZ broker over ~120 Polish library targets.
- IRSpy target registry — https://irspy.indexdata.com.
- NUKAT (union catalog) provides its Z39.50 parameters on request only.
English / international
| key | library | connection |
|---|---|---|
loc |
Library of Congress (Voyager) | z3950.loc.gov:7090/VOYAGER |
loc-lcdb |
Library of Congress (LCDB) | lx2.loc.gov:210/LCDB |
nkc |
Národní knihovna ČR | aleph.nkp.cz:9991/NKC |
demo |
Index Data demo (test) | z3950.indexdata.com:210/marc |
The Library of Congress also serves a MARC-8 database at
lx2.loc.gov:210/LCDB_MARC8 (pymarc transcodes it to Unicode). The Index Data
server is a tiny demo database, handy for testing this MCP without hitting a
real library.
Examples
search("demo", "computer") # tiny test database — smoke test
search("bn", "Lem Solaris") # Polish National Library
search("loc", "9780262033848", by="isbn") # Library of Congress, by ISBN
search("nkc", "Kafka", by="author", count=3) # Czech National Library
search("aleph.nkp.cz:9991/NKC", "Švejk") # same, as an ad-hoc target
Use with Claude Code / Claude Desktop
Claude Code (CLI)
Register the server with claude mcp add. The -s user scope makes it
available in all your projects; drop it for the current project only.
Straight from the public repo (no clone needed):
claude mcp add z3950 -s user -- uvx --from git+https://github.com/mpasternak/z3950-mcp z3950-mcp
From PyPI once released:
claude mcp add z3950 -s user -- uvx z3950-mcp
From a local checkout (for development):
claude mcp add z3950 -s user -- uv run --directory /path/to/z3950-mcp z3950-mcp
Remove it again with claude mcp remove z3950 -s user.
Claude Desktop (JSON config)
Add to claude_desktop_config.json (stdio transport):
{
"mcpServers": {
"z3950": {
"command": "uvx",
"args": ["--from", "git+https://github.com/mpasternak/z3950-mcp", "z3950-mcp"]
}
}
}
Adding catalogs
Append a Target(...) to _TARGETS in src/z3950_mcp/targets.py, or just pass
an ad-hoc host:port/database to search. Finding a library's Z39.50
coordinates: the IRSpy registry lists many;
some (e.g. NUKAT) provide them on request.
Development
uv run pytest # unit tests (offline)
uv run pytest -m integration # live tests against BN + LoC (network + yaz)
uv run ruff check .
Releasing
Releases publish to PyPI via
Trusted Publishing (OIDC — no
API tokens). Publishing a GitHub Release (or pushing a v* tag) triggers
.github/workflows/publish.yml, which builds and uploads from the pypi
environment. The PyPI project must have a matching trusted publisher
(repo mpasternak/z3950-mcp, workflow publish.yml, environment pypi).
License
MIT — see LICENSE.
Metadata
Release files for z3950-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| z3950_mcp-0.1.2.tar.gz | 86.3 kB | With provenance | Details for z3950_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| z3950_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for z3950_mcp-0.1.2-py3-none-any.whl |
Total release size: 100.2 kB
Release files / z3950_mcp-0.1.2.tar.gz
| Download URL | z3950_mcp-0.1.2.tar.gz |
|---|---|
| Size | 86.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ae0224f755d09d0655818bbb9f05d263931719f0e388f7a018210ab1fdee2d4
|
|
BLAKE2b-256 checksum How to use checksums |
333f8d07e1e48caa2366849a779537d0e902d9878a2cf7e3eb5da709b97ba5f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.
Transparency logRelease files / z3950_mcp-0.1.2-py3-none-any.whl
| Download URL | z3950_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c805c1362b6027abae2f5b0772d84c64233c1e9a77824d8e5e34f71f9b9fa556
|
|
BLAKE2b-256 checksum How to use checksums |
0a72fd817bcc563b93251a729a86fbcefc254398e6deb5be5eec20aa75af9d98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.
Transparency logSecurity for z3950-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for z3950_mcp-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.