Can AI agents automate Bibliofil?

Bibliofil is automatable today through Bibliotek-Systemer's documented WebAPI and library-standard protocols, not through a first-party MCP server or a Zapier, Make, Power Automate or n8n connector. Public WebAPI docs at dok.bibsyst.no describe REST JSON services for holdings, patron loans, reservations, renewals, fees and observation codes, plus OAI-PMH harvest and SRU 1.2 search. REST calls use HTTPS; integrator reads use Basic Authentication, and patron data or writes use OAuth 2.0 with an implicit token after patron login. The product page declares full NCIP support for interlibrary loan, national borrower cards and nationwide return. WebAPI access is a purchased per-library install, and patron-data use needs a data-processor agreement. The vendor states that not all patron functionality is covered by the APIs yet. Opened pages do not document a general staff cataloguing, acquisitions or circulation API. Z39.50 is documented as a maintained binary search protocol that the vendor recommends against for new work. SIP2 was not established as a Bibliofil interface. Ida, Frida and Fri meråpent stay outside this record. This record is not Axiell Quria, Mikromarc, Koha or Alma. Vendor documentation does not settle first-party MCP ownership. No official SDK, CLI or computer-use probe was established.

Best path today: api · Overall automatability: 5/10