Statsig MCP integration
Manage Statsig feature gates, dynamic configs, experiments, and lifecycle states.
Sign in, add Statsig in Apps, then choose the account your AI can use.
Tools
| Name | Description |
|---|---|
list_gatesList Statsig feature gates with common Console API filters. | List Statsig feature gates with common Console API filters. |
get_gateGet one Statsig feature gate by ID. | Get one Statsig feature gate by ID. |
create_gateCreate a Statsig feature gate. Rules and advanced fields can be supplied as Console API JSON. | Create a Statsig feature gate. Rules and advanced fields can be supplied as Console API JSON. |
update_gatePartially update a Statsig feature gate. | Partially update a Statsig feature gate. |
enable_gateEnable a Statsig feature gate. | Enable a Statsig feature gate. |
disable_gateDisable a Statsig feature gate. | Disable a Statsig feature gate. |
archive_gateArchive a Statsig feature gate. | Archive a Statsig feature gate. |
unarchive_gateUnarchive a Statsig feature gate. | Unarchive a Statsig feature gate. |
delete_gateDelete a Statsig feature gate. Prefer archive for normal lifecycle cleanup. | Delete a Statsig feature gate. Prefer archive for normal lifecycle cleanup. |
list_dynamic_configsList Statsig dynamic configs. | List Statsig dynamic configs. |
get_dynamic_configGet one Statsig dynamic config by ID. | Get one Statsig dynamic config by ID. |
create_dynamic_configCreate a Statsig dynamic config with JSON defaults and optional rules. | Create a Statsig dynamic config with JSON defaults and optional rules. |
update_dynamic_configPartially update a Statsig dynamic config. | Partially update a Statsig dynamic config. |
enable_dynamic_configEnable a Statsig dynamic config. | Enable a Statsig dynamic config. |
disable_dynamic_configDisable a Statsig dynamic config. | Disable a Statsig dynamic config. |
archive_dynamic_configArchive a Statsig dynamic config. | Archive a Statsig dynamic config. |
unarchive_dynamic_configUnarchive a Statsig dynamic config. | Unarchive a Statsig dynamic config. |
list_experimentsList Statsig experiments with pagination and common filters. | List Statsig experiments with pagination and common filters. |
get_experimentGet one Statsig experiment by ID. | Get one Statsig experiment by ID. |
update_experimentPartially update a Statsig experiment. | Partially update a Statsig experiment. |
archive_experimentArchive a Statsig experiment. | Archive a Statsig experiment. |
custom_api_callCall a Statsig Console API endpoint under /console/v1 using the stored Console API key. | Call a Statsig Console API endpoint under /console/v1 using the stored Console API key. |
Triggers
| Name | Description |
|---|---|
gate_updatedPoll for Statsig gates whose lastModifiedTime changed since the previous run. | Poll for Statsig gates whose lastModifiedTime changed since the previous run. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('statsig', 'list_gates', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'statsig',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a Statsig MCP server through Weavz?
Yes. Add the Statsig integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 22 Statsig actions.
What can an AI agent do with Statsig?
Available actions include List Gates, Get Gate, Create Gate, Update Gate, Enable Gate, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect Statsig to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Statsig, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use Statsig through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does Statsig require?
The catalog lists custom credentials for Statsig. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.
How do I review sensitive Statsig actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to Statsig?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
What Statsig triggers are available?
The catalog lists 1 triggers, including Gate Updated. Configure the trigger and your event handler before using incoming events to start work.
Connect Statsig in minutes
Get 20,000 free action executions every month. No credit card required.