Statsig

Commit a review of a dynamic config, APPLYING its proposed change to the live config. This is the step that actually mutates the config (e.g. updating rules/default_value, enabling/disabling, archiving, or deleting). Normally called after a different reviewer has approved the review. SELF-APPROVAL: an author cannot Approve_Dynamic_Config_Review on their own review — instead, to self-approve, the author commits their own still-pending review directly with this tool (this is the intended self-approval path). Self-commit succeeds only when the dynamic config permits self-approval and the acting user holds the "skip_config_review" permission. This tool bypasses precommit webhooks, so the acting user also needs "bypass_precommit_webhook"; otherwise this returns 403. Requires a key owned by a user. path_id = the dynamic config's name/ID; path_reviewID = the review ID.

Commit_Dynamic_Config_Review

Commit a review of an experiment (A/B test), APPLYING its proposed change to the live experiment. This is the step that actually mutates the experiment (e.g. starting / stopping it, shipping a decision, rolling out a group, or updating settings). Normally called after a different reviewer has approved the review. SELF-APPROVAL: an author cannot Approve_Experiment_Review on their own review — instead, to self-approve, the author commits their own still-pending review directly with this tool (this is the intended self-approval path). Self-commit succeeds only when the experiment's layer permits self-approval and the acting user holds the "skip_config_review" permission. This tool bypasses precommit webhooks, so the acting user also needs "bypass_precommit_webhook"; otherwise this returns 403. Requires a key owned by a user. path_id = the experiment's ID; path_reviewID = the review ID.

Commit_Experiment_Review

Commit a review of a gate (feature flag), APPLYING its proposed change to the live gate. This is the step that actually mutates the gate (e.g. updating rules, enabling/disabling, archiving, or deleting). Normally called after a different reviewer has approved the review. SELF-APPROVAL: an author cannot Approve_Gate_Review on their own review — instead, to self-approve, the author commits their own still-pending review directly with this tool (this is the intended self-approval path). Self-commit succeeds only when the gate permits self-approval and the acting user holds the "skip_config_review" permission. This tool bypasses precommit webhooks, so the acting user also needs "bypass_precommit_webhook"; otherwise this returns 403. Requires a key owned by a user. path_id = the gate's name/ID; path_reviewID = the review ID.

Commit_Gate_Review

Create an Autotune (multi-armed bandit) experiment that automatically shifts traffic toward the best-performing variant. Specify the variants (arms), the successEvent to optimize for, and the explorationWindow / attributionWindow / winnerThreshold parameters. Set isContextual=true to create a contextual multi-armed bandit (CMAB) that picks an arm per user-context; otherwise a standard MAB is created. Creating an Autotune begins reallocating live SDK traffic across the variants — review the variants and rollout settings before calling.

Create_Autotune

Open a review proposing a change to an autotune experiment. The change is NOT applied to the live autotune yet — it must be approved (Approve_Autotune_Review) and then committed (Commit_Autotune_Review). Set `type` to the kind of change and supply only the fields that type needs: start (optional start_date) / scheduled_start (start_time) / scheduled_start_edit (new_time) / reallocate — the autotune "reset" (optional reason) / make_decision (winning_group_id) / delete / disable_reviews_locally. Requires a key owned by a user. path_id = the autotune's ID.

Create_Autotune_Review

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_Dynamic_Config

Open a review proposing a change to a dynamic config. The change is NOT applied to the live config yet — it must be approved (Approve_Dynamic_Config_Review) and then committed (Commit_Dynamic_Config_Review). Provide a description, an optional set of requested reviewers (use Get_Dynamic_Config_Eligible_Reviewers to find valid IDs), and a `change` carrying exactly one change slot: the content bundle (`rules` and/or `default_value`, which may coexist), one verb field (e.g. is_enabled, is_archived, delete), `restore`, or one metadata field. Requires a key owned by a user (review actions are attributed to the key owner). path_id = the dynamic config's name/ID.

Create_Dynamic_Config_Review

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. For metrics, omit direction and hypothesizedValue unless the user explicitly asks for one-sided testing or one-sample testing. Metric direction enables one-sided testing; hypothesizedValue enables one-sample testing against a fixed baseline.

Create_Experiment

Open a review proposing a change to an experiment (A/B test). The change is NOT applied to the live experiment yet — it must be approved (Approve_Experiment_Review) and then committed (Commit_Experiment_Review). Set `type` to the kind of change (start / stop / pause / restart / abandon / archive / delete / make_decision / rollout / schedule_rollout / reallocate / change_enabled_groups / unarchive / update_owners / update_team / update_settings / update_overrides / update_target_applications / update_allowed_reviewers / update_default_impact_multiplier / scheduled_start / scheduled_start_edit / disable_reviews_locally) and supply only the fields that type needs (e.g. make_decision → winning_group_id; rollout → group_id + rollout_percentage; update_owners → owners; update_settings → settings). Requires a key owned by a user. path_id = the experiment's ID.

Create_Experiment_Review

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_Gate

Open a review proposing a change to a gate (feature flag). The change is NOT applied to the live gate yet — it must be approved (Approve_Gate_Review) and then committed (Commit_Gate_Review). Provide a description, an optional set of requested reviewers (use Get_Gate_Eligible_Reviewers to find valid IDs), and a `change` carrying EXACTLY ONE proposed operation (e.g. rules, is_enabled, is_archived, delete). Requires a key owned by a user (review actions are attributed to the key owner). path_id = the gate's name/ID.

Create_Gate_Review

Create a new layer, including its name, ID type, and optional target apps or team ownership.

Create_Layer

Create a new Param Store (a reusable, named collection of typed parameters) in this Statsig project. Provide a name (the in-code identifier), a displayName, and a description. The store is created empty — add parameters afterward with Update_Param_Store. Optionally set targetAppIDs, tags, and team.

Create_Param_Store

Create a new Prompt (a specialized AI Config for managing and versioning LLM prompts) in the Statsig console. A Prompt is created by name (the in-code identifier); optionally set a displayName, description, target apps, owning team, and tags. Add prompt content afterward with Create_Prompt_Version.

Create_Prompt

Create a new version of an existing Prompt. Provide the prompts array (each entry has a role of system, user, or assistant and its content), and optionally the model, provider, temperature, top_p, max_tokens, frequency_penalty, presence_penalty, description, eval_model, and workflow fields (workflow_body, workflow_headers, auth_workflow_headers). The version name (in-code identifier) is set via name.

Create_Prompt_Version

Create a new segment, including its name, type, optional ID, ID type, and rules for rule-based segments.

Create_Segment

Delete an experiment (A/B test) by ID. Destructive and irreversible — confirm the ID before calling. On a team that requires reviews, prefer proposing the deletion through review (Create_Experiment_Review with type "delete" → approve → commit) instead of deleting directly. Requires a key owned by a user. path_id = the experiment's ID.

Delete_Experiment

Delete a Param Store by name. Destructive and irreversible — it removes a store that SDKs may be reading. Confirm the name before calling.

Delete_Param_Store

Edit an in-flight autotune review's metadata — description and/or requested reviewers. Supply any subset; an omitted field keeps the review's current value, and an empty body is rejected. Autotune reviews have no editable "content" (to change the proposed change, cancel and recreate). The review must still be mutable (pending or accepted). Requires a key owned by a user. path_id = the autotune's ID; path_reviewID = the review ID.

Edit_Autotune_Review

Edit an in-flight dynamic config review's metadata (description, requested reviewers) and/or its proposed `change`. Supply any subset; an empty body is rejected. The review must still be mutable (pending or accepted); content (`change`) can only be edited while pending and cannot change the review's type. Requires a key owned by a user. path_id = the dynamic config's name/ID; path_reviewID = the review ID.

Edit_Dynamic_Config_Review

Edit an in-flight experiment (A/B test) review's metadata — description and/or requested reviewers. Supply any subset; an omitted field keeps the review's current value, and an empty body is rejected. Experiment reviews have no editable "content" (to change the proposed change, cancel and recreate). The review must still be mutable (pending or accepted). Requires a key owned by a user. path_id = the experiment's ID; path_reviewID = the review ID.

Edit_Experiment_Review

Edit an in-flight gate (feature flag) review's metadata (description, requested reviewers) and/or its proposed `change`. Supply any subset; an empty body is rejected. The review must still be mutable (pending or accepted); content (`change`) can only be edited while pending and cannot change the review's type. Requires a key owned by a user. path_id = the gate's name/ID; path_reviewID = the review ID.

Edit_Gate_Review

List audit logs for this Statsig project. Supports filtering by id, sorting, tags, date range, and pagination.

Get_Audit_Logs

List the users and reviewer groups eligible to approve/reject a review of this autotune experiment. Use this to pick valid reviewer_ids / reviewer_group_ids when creating or editing an autotune review. The response carries everyone_eligible (true when anyone may review), users (the flattened, deduped set of eligible individuals), and groups (each with its member user_ids). Note: project admins can always review and are NOT enumerated here. path_id = the autotune's ID.

Get_Autotune_Eligible_Reviewers

Get a single review for an autotune experiment by its review ID, including its status, proposed change type, author, and requested reviewers. A review is a proposed change that goes through an approve → commit lifecycle before it is applied. path_id = the autotune's ID; path_reviewID = the review ID (from Get_List_of_Autotune_Reviews or Create_Autotune_Review).

Get_Autotune_Review_by_ID

Bootstrap the authenticated Statsig MCP session. Returns bounded organization, selected project, environment, effective API-key permissions, review settings, accessible product areas, project environments, event sources, metrics, default timezone, and relevant links. The API key already selects one project, so no project ID is required. Use scope for common bundles and fields/limit to request only the context sections you need.

Get_Context

Get the details (including rules, return values, and more) for a Dynamic Config (static, targetable JSON) in the Statsig console.

Get_Dynamic_Config_Details_by_ID

List the users and reviewer groups eligible to approve/reject a review of this dynamic config. Use this to pick valid reviewer_ids / reviewer_group_ids when creating or editing a dynamic config review. The response carries everyone_eligible (true when anyone may review), users (the flattened, deduped set of eligible individuals), and groups (each with its member user_ids). Note: project admins can always review and are NOT enumerated here. path_id = the dynamic config's name/ID.

Get_Dynamic_Config_Eligible_Reviewers

Get a single review for a dynamic config by its review ID, including its status, proposed change, author, and requested reviewers. A review is a proposed change to the dynamic config that goes through an approve → commit lifecycle before it is applied. path_id = the dynamic config's name/ID; path_reviewID = the review ID (from Get_List_of_Dynamic_Config_Reviews or Create_Dynamic_Config_Review).

Get_Dynamic_Config_Review_by_ID

List historical versions of a Dynamic Config (static, targetable JSON object) to reconstruct a timeline of how it changed — rules, return values, defaults, and metadata across edits. Useful for debugging when dynamic config behavior changed and what changed it.

Get_Dynamic_Config_Version_History

Get details including parameters (return values), groups, status & more of an experiment in Statsig. Use query_fields to return only specific top-level fields and keep the response small.

Get_Experiment_Details_by_ID

List the users and reviewer groups eligible to approve/reject a review of this experiment (A/B test). Use this to pick valid reviewer_ids / reviewer_group_ids when creating or editing an experiment review. The response carries everyone_eligible (true when anyone may review), users (the flattened, deduped set of eligible individuals), and groups (each with its member user_ids). Note: project admins can always review and are NOT enumerated here. path_id = the experiment's ID.

Get_Experiment_Eligible_Reviewers

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_Experiment_Metric_Dimension_Results

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_Experiment_Overall_Results

Get a single review for an experiment (A/B test) by its review ID, including its status, proposed change type, author, and requested reviewers. A review is a proposed change that goes through an approve → commit lifecycle before it is applied. path_id = the experiment's ID; path_reviewID = the review ID (from Get_List_of_Experiment_Reviews or Create_Experiment_Review).

Get_Experiment_Review_by_ID

List historical versions of an experiment (AB Test) to reconstruct a timeline of how it changed — groups, allocation, status, parameters, and metadata across edits. Useful for debugging when experiment behavior changed and what changed it.

Get_Experiment_Version_History

Get all details about a gate (feature flag) like its rules, idType, and more, from the Statsig Console. To judge whether a feature is actually live for a user, check status and isEnabled BEFORE reasoning about rules: when isEnabled is false the rules are NOT evaluated and every user receives the same blanket value — status "Launched" means all users pass (gate returns true) and status "Disabled" means all users fail (gate returns false). The rules apply only when isEnabled is true (status "In Progress"), where a user passes only if they match a passing rule. status "Archived" means the gate is retired.

Get_Gate_Details_by_ID

List the users and reviewer groups eligible to approve/reject a review of this gate (feature flag). Use this to pick valid reviewer_ids / reviewer_group_ids when creating or editing a gate review. The response carries everyone_eligible (true when anyone may review), users (the flattened, deduped set of eligible individuals), and groups (each with its member user_ids). Note: project admins can always review and are NOT enumerated here. path_id = the gate's name/ID.

Get_Gate_Eligible_Reviewers

Get the metric results for a given gate and rule in the gate

Get_Gate_Results

Get a single review for a gate (feature flag) by its review ID, including its status, proposed change, author, and requested reviewers. A review is a proposed change to the gate that goes through an approve → commit lifecycle before it is applied. path_id = the gate's name/ID; path_reviewID = the review ID (from Get_List_of_Gate_Reviews or Create_Gate_Review).

Get_Gate_Review_by_ID