BookStack + Memtro

Only when you ask, and only what it has been granted: create a page in a book or chapter; create a chapter in a book; create a book; comment on a page; replace a page's name, body or tags; archive a comment; delete a page, chapter or book (to the recycle bin); delete a comment; rename a chapter or book, change its description or tags, or move a chapter to another book; create a shelf, change its name, description, tags or books, or delete it (to the recycle bin; its books stay); edit a comment's text, or unarchive a comment; attach a link to a page, or delete an attachment permanently. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

Host, Token ID and Token secret. In BookStack open your profile → Edit profile → API Tokens → Create Token, name it Memtro, choose an expiry and copy the ID and secret. The button needs the Access System API permission from an administrator.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in BookStack, choosing the same kinds; the tab shows BookStack's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.