Statsig

Bring your Statsig workspace into ChatGPT. Product builders can now explore, manage, and create Statsig experiments, feature gates, dynamic configs, and more directly in ChatGPT conversations. Ask things like: “Move this experiment to 50% rollout.” “Turn on this feature gate for all users.” “Show me which dynamic configs changed this week.” "Explain how the DAU metric is defined.” You can both read and write to Statsig: inspect experiment settings, read metric definitions, update allocations, toggle feature flags, edit targeting rules, and modify dynamic config values directly from ChatGPT. The app connects through Statsig’s MCP server and honors your existing Statsig permissions, so you only see and change what you’re authorized to access—across projects, environments, and teams.

View in the ChatGPT registry

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Developer Tools
Primary Subcategory: Product Analytics & Experimentation
Secondary Subcategories: None listed
Brand: Statsig
Access: Account required
First tracked: 2026-04-14
Tool count: 34
Geography: US

ChatGPT Plugin Discoverability Score

ChatGPT organic discovery is not live yet

Statsig is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.

Get notified when your score goes live

Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.

No spam. Unsubscribe any time.

Talk to our team

Primary Subcategory

Competing in ChatGPT Product Analytics & Experimentation

View Category

Listed in alphabetical order

Primary Subcategory

AmplitudeOrganic discovery is pendingGet the score at launch

Amplitude EUOrganic discovery is pendingGet the score at launch

ClicsOrganic discovery is pendingGet the score at launch

Customer Journey AnalyticsOrganic discovery is pendingGet the score at launch

KrystalViewOrganic discovery is pendingGet the score at launch

StatsigOrganic discovery is pendingGet the score at launch

Score explained

How the Discoverability Score works

Organic discovery scoring for Statsig on ChatGPT is not live yet. The score will use measured agent conversations when it launches.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

34 tools agents can invoke

Create a new Dynamic Config (static, targetable JSON object) in the Statsig console, including targeting rules, its ID (how we'll refer to it in-code) and its IDtype, which it'll randomize users on. CRITICAL CONSTRAINTS: - the return value for each variant must be set with returnValueJson5. - Always include DefaultValue field in the POST request
Create an experiment, including its ID (which is how we refer to it in-code), its groups (test/control, and return values) and the ID type it should randomize users on.
Create a new gate (feature flag), including its rules (who should pass it) its ID (how we'll refer to it in-code) and its IDtype, which it'll randomize users on.
Create a new layer, including its name, ID type, and optional target apps or team ownership.
Create a new segment, including its name, type, optional ID, ID type, and rules for rule-based segments.
Get Experiment Summary charts and underlying data.
List audit logs for this Statsig project. Supports filtering by id, sorting, tags, date range, and pagination.
Get the details (including rules, return values, and more) for a Dynamic Config (static, targetable JSON) in the Statsig console.
Get details including parameters (return values), groups, status & more of an experiment in Statsig.
Get topline and dimensional breakdown results for one specific experiment metric. Use this when you already know the metric ID and need that metric broken down by dimensions. Do not use this tool for an experiment-wide summary across all pulse metrics; use Get_Experiment_Overall_Results instead.
Get overall pulse results for an experiment across all pulse metrics. Use this when you need the experiment-wide topline view or a cross-metric summary. Do not use this tool when you need the dimensional breakdown for one specific metric; use Get_Experiment_Metric_Dimension_Results instead.
Get all details about a gate (feature flag) like its rules, IDtype, and more, from the Statsig Console.
Get the metric results for a given gate and rule in the gate
Get all details about a layer, including its parameters and metadata, from the Statsig Console.
List all Dynamic Configs (static, targetable JSON objects) in this Statsig project. The API enforces a maximum query_limit of 100. If query_limit is not provided, default to 100 (or fewer) and never exceed 100.
List all experiments (AB Tests) in this Statsig project. The API enforces a maximum query_limit of 100. If query_limit is not provided, default to 100 (or fewer) and never exceed 100.
List all gates (feature flags) in this Statsig project. The API enforces a maximum query_limit of 100. If query_limit is not provided, default to 100 (or fewer) and never exceed 100.
List all layers in this Statsig project. The API enforces a maximum query_limit of 100. If query_limit is not provided, default to 100 (or fewer) and never exceed 100.
List all metric sources in this Statsig project. The API enforces a maximum query_limit of 100. If query_limit is not provided, default to 100 (or fewer) and never exceed 100.
List all metrics in this Statsig project. The API enforces a maximum query_limit of 100. If query_limit is not provided, default to 100 (or fewer) and never exceed 100.
List param stores in this Statsig project. The API enforces a maximum query_limit of 100. If query_limit is not provided, default to 100 (or fewer) and never exceed 100.
List all segments in this Statsig project.
Get the full definition for a metric in Statsig, including its type, source, and configuration details.
Get a param store by name, including its description, typed parameters, and metadata.
Get all details about a segment in the Statsig Console.
Start code cleanup for a stale experiment by name, which creates a PR to remove the experiment from your codebase.
Start code cleanup for a gate by name, which creates a PR to remove the gate from your codebase.
Fully update a dynamic config, replacing everything the dynamic config currently has on the Statsig console with the data included in this POST request. Use the GET option to gather the attributes of the dynamic config, edit them, then use this tool. CRITICAL CONSTRAINTS: - the return value for each variant must be set with returnValueJson5. - Always include DefaultValue field in the POST request
Fully update an experiment, replacing everything the experiment currently has on the Statsig console with the data included in this POST request. Use the GET option to gather the attributes of the experiment, edit them, then use this Tool.
Fully update a gate, replacing everything the gate currently has on the Statsig console with the data included in this POST request. Use the GET option to gather the attributes of the gate, edit them, then use this tool.
Fully update a layer, replacing everything the layer currently has on the Statsig console with the data included in this POST request. Use the GET option to gather the attributes of the layer, edit them, then use this tool.
Update a Statsig segment using the appropriate segment endpoint. Supports rule-based rule updates and add operations for ID list / user store ID list segments via params.query_operation.
Fetch the full document for a search result id. Use the id returned by search.
Search the Statsig MCP data source and return relevant results. Use the fetch tool to retrieve full documents.

Statsig FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Statsig alternatives on ChatGPT?

As of 2026-08-14, Statsig competes with Amplitude, Amplitude EU, Clics, Customer Journey Analytics, KrystalView, Mixpanel, Pendo, PostHog, Subtext, Userflow, Wingify in ChatGPT Product Analytics & Experimentation, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.