Featurebase + Memtro

Only when you ask, and only what it has been granted: create a feedback request on a board; edit a request: title, content, board, status, tags, ETA, assignee or visibility; delete a request with its comments and votes; add an upvote to a request for a named person; comment on a request or update, publicly or privately; delete a comment; close, snooze, reopen, assign or rename a support conversation; reply to a customer in a conversation, or add an internal note; leave a reply or note draft in an admin's composer; tag a conversation; create a draft changelog update; publish or schedule a changelog update, optionally emailing subscribers. 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. An hourly sync anchors recently changed Featurebase records into memory as entities.

API key. In Featurebase, open Settings, API and create a key, which starts sk_. Changelog actions need the key's owner to have a full seat and the manage_changelogs permission.

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Featurebase for you. 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.