bibliocommons-mcp
MCP server for placing holds, searching, and managing your account at BiblioCommons-powered public libraries.
Install
pipx install bibliocommons-mcp
Requires Python 3.11+.
Quick Start
bibliocommons-mcp init
claude mcp add bibliocommons bibliocommons-mcp --scope user
init walks the prompts, validates live against the gateway, and writes the config file for you. Manual setup: docs/configuration.md. For Claude Desktop, Cursor, or other MCP clients: docs/mcp-clients.md.
Try asking
Place a hold on something at my branch.
Show my current holds with queue positions.
What's due back this week?
Cancel a hold.
Tools
All mutation tools accept a list of IDs/refs — pass [id] for the common single-item case.
| Tool | Description |
|---|---|
search |
Search the catalog, optionally filtered by format |
availability |
Show per-branch status for a bib |
place_hold |
Place physical holds at your pickup branch |
borrow_digital |
Borrow one or more available digital items |
place_digital_hold |
Join the Libby waitlist for unavailable digital items |
list_holds |
Show current holds and queue positions |
ready_for_pickup |
Show only the holds waiting at your branch |
cancel_hold |
Cancel holds (native bulk; one DELETE per call) |
list_loans |
Show checkouts with due dates |
renew_loan |
Renew physical checkouts (native bulk; one PATCH per call) |
check_in_loan |
Return digital checkouts early |
list_branches |
List all branches at your library |
library_health |
Check login and report hold quotas |
Library compatibility
The same gateway serves every BiblioCommons-powered library — see docs/known-libraries.md for what's been verified. If yours isn't listed, file a compatibility report once you try it.
Requirements
- Python 3.11+
- A BiblioCommons library account in good standing (card + PIN)
- The library must run on BiblioCommons (visit
{name}.bibliocommons.comand confirm)
Further reading
docs/architecture.md— gateway client design and API quirksdocs/format-codes.md— format facet codesdocs/troubleshooting.md— common errors and fixesdocs/roadmap.md— what's planned nextdocs/releasing.md— automated release flow
1 maintainer
Metadata
1 maintainer
Release files for bibliocommons-mcp 0.6.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 | |
|---|---|---|---|---|
| bibliocommons_mcp-0.6.2.tar.gz | 893.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bibliocommons_mcp-0.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / bibliocommons_mcp-0.6.2.tar.gz
| Download URL | bibliocommons_mcp-0.6.2.tar.gz |
|---|---|
| Size | 893.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6312d7cd9e992378476bb99e39e15a72e5f5b661f622788a903fd37f35bc5be7
|
|
BLAKE2b-256 checksum How to use checksums |
213af8297fd8acad821827f8ba3f2f6e0affdcc3b9f09e3c618c5bafe99699fc
|
| 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 28, 2026.
Transparency logRelease files / bibliocommons_mcp-0.6.2-py3-none-any.whl
| Download URL | bibliocommons_mcp-0.6.2-py3-none-any.whl |
|---|---|
| Size | 496.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2aca75fbeb55989109ccca8e07077a10020cbfd9f3ad05e69c61bf78f7218346
|
|
BLAKE2b-256 checksum How to use checksums |
d173c1762b4b84a1fb0c960d3e21d742facf1154e4d5dbde11d3ddd869b5e425
|
| 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 28, 2026.
Transparency logSecurity for bibliocommons-mcp 0.6.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 bibliocommons_mcp-0.6.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 28, 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.
