LaunchDarkly + Memtro

Only when you ask, and only what it has been granted: turn a flag on or off in one environment; change a flag's individual targets, fallthrough (variation or rollout) or off variation in one environment; create a feature flag; rename a flag, change its description, tags, temporary status or maintainer; archive or restore a flag; delete a flag permanently; request approval for a flag change, notifying the reviewers named; approve, decline or comment on an approval request; apply an approved approval request; create a segment in one environment; add or remove context keys in a segment's included or excluded list; delete a segment 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. An hourly sync anchors recently changed LaunchDarkly records into memory as entities.

Access token. In LaunchDarkly open Organization settings (gear) → Authorization → Tokens → Create token. The Reader role covers everything Memtro reads and cannot change a flag, and the Writer role is needed only if flag and segment changes are granted.

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 LaunchDarkly 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.