Release day check
Sarah Chen, product manager at Acme Ltd, asked whether newCheckout was on in production. Memtro read the flag values for that environment and answered that it served true, with two targeting rules, last changed on Tuesday.
Is this ConfigCat flag on in production, and who changed it?
ConfigCat holds your feature flags. Memtro reads your products, configs and environments, the flags in each config, what each boolean or number flag serves in an environment, how many targeting rules apply, and the audit log of who changed what and why. When asked, and once an administrator has granted the action by name, it can turn a flag on or off or change what it serves, which live apps pick up within their polling interval, open, approve, apply or close change requests, create flags, tags, configs and environments, and permanently delete a flag. Text setting values are withheld.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ConfigCat tool, reads what it needs, and answers with the source cited.
These tools change something in ConfigCat. 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 ConfigCat, choosing the same kinds; the tab shows ConfigCat's own steps. Each event can start a job, with the event as its input. ConfigCat signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce ConfigCat 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 newCheckout on in production?
Who changed the pricing flag this week?
Which flags in the web config are tagged beta?
How many targeting rules does darkMode have in Test?
Turn darkMode on in Test
Sarah Chen, product manager at Acme Ltd, asked whether newCheckout was on in production. Memtro read the flag values for that environment and answered that it served true, with two targeting rules, last changed on Tuesday.
Tom Reilly, engineering lead at Northwind, asked Memtro to turn off newCheckout in Production after a spike in errors. Production needs approval, so Memtro opened a change request proposing false. Once Priya Sharma approved it, Memtro applied it and live apps stopped serving the new checkout. The change shows in the audit log.
The teams that lean on ConfigCat most, a question each of them asks, and what they connect beside it.
A record in ConfigCat 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.
In app.configcat.com, open My account → Public API credentials. These are not your ConfigCat login and act with your permissions, so a user in read-only permission groups keeps Memtro to reading, and the actions need a user who may make those changes.
Add new credentials named Memtro, then copy the Basic auth user name and password. The password is shown once.
In Memtro, open Connections → ConfigCat and paste them as Basic auth user name and Basic auth password.
Ask: is newCheckout on in production?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ConfigCat tools are the same everywhere.
Only when you ask, and only what it has been granted: turn a flag on or off, or change its default or one targeting rule's served value, in one environment; create a feature flag or setting in a config; rename a flag, change its hint or add tags to it; delete a flag permanently from every environment; open a change request proposing a flag value in an environment that needs approval; approve a change request; apply a change request, publishing its changes immediately; close a change request without applying it; comment on a change request; create a tag, a config or an environment in a product. 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.
Basic auth user name and Basic auth password. In app.configcat.com, open My account → Public API credentials. These are not your ConfigCat login and act with your permissions, so a user in read-only permission groups keeps Memtro to reading, and the actions need a user who may make those changes.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in ConfigCat, choosing the same kinds; the tab shows ConfigCat'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