01 · Records and state owned
Experiments, feature gates, dynamic configs, segments, metrics, dashboards and audit-log operations; GET and POST tools
Statsig
Statsig
Curated major addition platform in experimentation, feature flags, and product analytics with material relevance to the Marcom operating stack and a first-party developer surface.
Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Experiments, feature gates, dynamic configs, segments, metrics, dashboards and audit-log operations; GET and POST tools
03 · Actions and write paths
The targeted review confirmed this Statsig capability surface: Experiments, feature gates, dynamic configs, segments, metrics, dashboards and audit-log operations; GET and POST tools. It did not normalize every mutation tool. Treat writes as unapproved until each current tool, scope, plan and approval behavior is verified.
04 · Authentication and permissions
Official docs distinguish authenticated project-data MCP from public docs MCP; write tools require write-capable credentials. Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary.
05 · Monitoring, approval, and recovery
Official docs distinguish authenticated project-data MCP from public docs MCP; write tools require write-capable credentials. Official docs distinguish authenticated project-data MCP from public docs MCP; write tools require write-capable credentials.
06 · Gaps and implementation limits
Official docs distinguish authenticated project-data MCP from public docs MCP; write tools require write-capable credentials.
First-party access
Documented surfaces
Warehouse-native SQL ↗Statsig Warehouse Native supports SQL that runs in the customer's warehouse. Data access, compute cost, schemas, roles, and experiment configuration remain governed by the connected warehouse and Statsig setup.Source: Statsig warehouse SQLMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Verified first-party provider MCPVendor-hosted remote MCPCurrent documented service
Role: provider
Read scope: Experiments, feature gates, dynamic configs, segments, metrics, dashboards and audit-log operations; GET and POST tools
Write scope: Write scope was not separately normalized in this pass; inspect the official tool catalog before enabling actions.
Authentication: Official docs distinguish authenticated project-data MCP from public docs MCP; write tools require write-capable credentials.
Approval boundary: Official docs distinguish authenticated project-data MCP from public docs MCP; write tools require write-capable credentials.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Statsig ships these experiences.
Single-platform patterns
- Experiment, gate, and release-governance cockpit
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- Statsig + warehouse or semantic layer: executive insight brief
- Statsig + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCPRepresentative source
https://docs.statsig.com/integrations/mcp/overview ↗Official docs distinguish authenticated project-data MCP from public docs MCP; write tools require write-capable credentials.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://docs.statsig.com/console-api/introduction ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://docs.statsig.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.statsig.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Warehouse-native SQLTargeted review
Statsig warehouse SQL ↗Statsig Warehouse Native supports SQL that runs in the customer's warehouse. Data access, compute cost, schemas, roles, and experiment configuration remain governed by the connected warehouse and Statsig setup.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.