Is that flag on in Production, and who changed it last?
From Flagsmith, Memtro reads your projects, environments, flags with their state per environment, segments, tags and the audit log of who changed what. Segment rules stay out, as they can name end users. When asked and once an administrator has granted the action by name, it can turn a flag on or off, set its value, override it for a segment, and create flags, segments and tags. A change in Production reaches your users at their next poll. Deleting a flag is permanent, removing it from every environment.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Flagsmith tool, reads what it needs, and answers with the source cited.
These tools change something in Flagsmith. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Flagsmith, choosing the same kinds; the tab shows Flagsmith's own steps. Each event can start a job, with the event as its input. Flagsmith signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Flagsmith is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Is new_checkout on in Production?
Who changed flags in the Web project this week?
Which flags in the Web project are archived?
Which segments override a flag?
Turn new_checkout off in Production.
Dan Fletcher, engineering lead at Acme Ltd, asked whether new_checkout was on in Production before a launch. Memtro read the flag's state in Production and when it last changed. It then named who changed it from the audit log.
Priya Sharma, a product engineer at Northwind, saw checkout errors and asked Memtro to turn new_checkout off in Production. Memtro toggled the flag off in that environment, and every app using Production picked up the change at its next poll. The audit log recorded the change.
The teams that lean on Flagsmith most, a question each of them asks, and what they connect beside it.
A record in Flagsmith is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Flagsmith, open your organisation name at the top, then API Keys → Create API Key.
On Enterprise or Scale-Up, give the key a role with only the permissions Memtro should have: view-only keeps it read-only. Otherwise the key acts as an organisation administrator. An environment's SDK key will not work.
In Memtro, open Connections → Flagsmith, paste the key into Organisation API key, and fill API host only if you self-host.
Ask: is new_checkout on in Production?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Flagsmith tools are the same everywhere.
Only when you ask, and only what it has been granted: turn a flag on or off in one environment; set a flag's value (and optionally its on/off state) in one environment; override a flag for a segment in one environment; create a feature flag in a project; change a flag's description or tags, or archive or unarchive it; delete a feature flag from every environment, permanently; create a segment of users defined by rules; create a tag for flags. 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.
Organisation API key. In Flagsmith, open your organisation name at the top, then API Keys → Create API Key.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Flagsmith, choosing the same kinds; the tab shows Flagsmith'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.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
