Cost control: a monthly token allowance for each modelSee how it works
memtro
Start for free

Statsig + Memtro

Ask Statsig who turned a feature gate off, and how an experiment is going.

Connect Statsig with a Console API key and Memtro reads feature gates with their rules and owners, experiments, and the project's audit log of who changed what. Staff email addresses and the user ids in targeting rules are never read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can create tags and gates, enable, disable or launch a gate, which every user feels at once, and create, start or decide experiments. Deciding an experiment or deleting a gate cannot be undone.

Connect StatsigStart for freeReference
In Memtro

What you can do with Statsig in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Statsig tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Feature gates filtered by tag, type or name, with enabled state, owner, checks per hour and rule count
  2. 02One gate's rules with pass percentage, environments and the kind of conditions, never the user lists
  3. 03Experiments with hypothesis, status, groups and sizes, primary and secondary metrics, and the decision and why
  4. 04The audit log of who changed which gate or experiment and when, up to 90 days back
  5. 05When asked and granted, creates or renames tags, creates gates, enables, disables or launches a gate for every user at once, forces named users to pass or fail, and archives or permanently deletes a gate
  6. 06When asked and granted, creates and starts experiments, which assigns real users to groups, archives them, or decides one by shipping a group to everyone, which ends it for good

Acts when asked

When you ask it to

These tools change something in Statsig. 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.

  1. 01Create a tag
  2. 02Rename or redescribe a tag
  3. 03Create a feature gate (passes nobody until it has rules)
  4. 04Enable a feature gate (users see it at once)
  5. 05Disable a feature gate (users lose it at once)
  6. 06Launch a feature gate to everyone
  7. 07Archive a feature gate
  8. 08Delete a feature gate (permanent)
  9. 09Force named user ids to pass or fail a gate
  10. 10Create an experiment in setup
  11. 11Start an experiment (assigns real users)
  12. 12Finish an experiment by shipping one group
  13. 13Archive an experiment

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Statsig, choosing the same kinds; the tab shows Statsig's own steps. Each event can start a job, with the event as its input. Statsig signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01A gate, experiment or config was changed in the console
  • 02A user was checked against a gate
  • 03A user was assigned to an experiment group
  • 04A user was served a dynamic config
In practice

Ask it like you would a colleague

Once Statsig 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.

Statsig + Memtro

  • Who turned the new checkout gate off, and when?

  • Which feature gates are stale?

  • How is the onboarding experiment going, and what are its metrics?

  • What changed in Statsig in the hour before the incident?

  • Disable the new checkout gate now

01

Who flipped the flag

After a drop in sign-ups the product lead asks what changed. Memtro reads the audit log and finds the new onboarding gate was disabled at 15:20 on Thursday by Dan Fletcher, an hour before the drop began.

02

Pulling the kill switch

Checkout errors spike at Acme just after a release and Priya Sharma asks Memtro to turn the new payment flow off. Memtro disables the new checkout gate, so it fails for every user at once and they fall back to the old flow, then shows her who last changed it.

Teams

Where it fits

The teams that lean on Statsig most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Statsig 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.

Also in Engineering and operations

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withConsole API key
  1. 1

    In console.statsig.com open Project Settings → API Keys and generate a Console API key, not a server or client SDK key

  2. 2

    A read-only key is enough unless Memtro should change gates, experiments or tags

  3. 3

    Copy the key, then in Memtro open Connections → Statsig, paste the Console API key and connect

  4. 4

    Ask who changed the checkout gate this week

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Statsig tools are the same everywhere.

Set it up as an MCP serverClients and agents
FAQ

Questions

Can Memtro change anything in Statsig?+

Only when you ask, and only what it has been granted: create a tag; rename or redescribe a tag; create a feature gate (passes nobody until it has rules); enable a feature gate (users see it at once); disable a feature gate (users lose it at once); launch a feature gate to everyone; archive a feature gate; delete a feature gate (permanent); force named user ids to pass or fail a gate; create an experiment in setup; start an experiment (assigns real users); finish an experiment by shipping one group; archive an experiment. 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.

Who can use a Statsig connection?+

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.

Does Memtro store my Statsig data?+

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.

How do I connect Statsig?+

Console API key. In console.statsig.com open Project Settings → API Keys and generate a Console API key, not a server or client SDK key.

Can Statsig start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Statsig, choosing the same kinds; the tab shows Statsig'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.

Connect Statsig in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Start for freePricing

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

Start for freeGetting started

7-day free trial · card on file, nothing charged until it ends · cancel any time