Typesense + Memtro

Only when you ask, and only what it has been granted: create a document in a collection; upsert a document, replacing whole any document with the same id; update fields of one document; delete one document; delete the documents in a collection that match a filter; import documents in bulk (create, update, upsert or emplace); create a collection; delete a collection with all its documents; change a collection's schema: add or drop fields, link synonym or curation sets; update the same fields on up to 100 listed documents; create or repoint an alias to a collection; delete an alias; create or replace a synonym set, or one synonym in it; delete a synonym set or one synonym; create or replace a curation set, or one curation (pin or hide results for a query); delete a curation set or one curation; create or replace a stopwords set; clear the search result cache. 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 and API key. Make a key for Memtro (Typesense Cloud → Cluster → Generate API Keys, or POST /keys with the admin key) with collections:list, collections:get, documents:search and documents:get, limited to the right collections. Add documents:create, documents:upsert, documents:update, documents:import and documents:delete, or collections, aliases, synonym and curation actions, only where Memtro may change them.