01 · Records and state owned
Audit logs; dynamic configs; experiments; autotunes; feature gates; layers; metrics and metric sources; parameter stores; segments; reviews; logs and observability.
Statsig
Statsig
Statsig is a major experimentation-control surface because its first-party MCP can inspect experiment evidence and operational state while authorized write tools can create, update, or delete gates, configs, experiments, and related project objects.
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
Read tools expose authorized Statsig project configuration and operational data across the listed MCP capability areas; read-only users can connect and use the full read-tool set.
03 · Actions and write paths
Write-capable credentials can use POST tools to create and update project entities, and Statsig documents cleanup workflows that bulk create or delete gates. Exact mutations follow the current tool catalog and key permissions.
04 · Authentication and permissions
The hosted project-data MCP supports OAuth or API-key setup at `https://api.statsig.com/v1/mcp`. OAuth relies on Personal Console API Keys, which an organization owner must enable for the user's role; personal keys inherit that role's access conditions.
05 · Monitoring, approval, and recovery
Personal Console API Keys preserve per-user role scope and support cleaner audit attribution than a shared Console API Key. Statsig also exposes audit logs and reviews through MCP; BYO-UI should require explicit confirmation before delete or bulk mutation tools unless a verified project review rule covers that action.
06 · Limits and caveats
Authenticated project MCP and public Docs MCP are different services. The Docs MCP cannot access project data or writes, serves English documentation only, supports Streamable HTTP only, exposes no prompts/resources, and rate-limits each client; project write availability depends on the credential's permissions.
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 support
Official MCP serverVendor-hosted authenticated project MCP plus separate public documentation MCPCurrent documented service
Support: Official MCP server
Read scope: List and inspect authorized experiments, gates, configs, layers, segments, metrics, parameter stores, reviews, audit events, and observability records through Statsig read tools.
Write scope: With write permission, create or update experiments, gates, configs, and other supported entities and invoke documented deletion workflows; a read-only credential exposes none of those write tools.
Authentication: Vendor-hosted remote HTTP MCP with OAuth or API-key authentication for project data; a separate public documentation endpoint requires no key.
Approval boundary: Statsig documentation proves credential-gated writes but does not establish a universal human approval gate for MCP mutations. For BYO-UI, present an explicit review step for gate/config/experiment creation, rollout-affecting edits, and every bulk or delete operation.
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 customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Statsig ships them.
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.
7 recorded sources
MCPRepresentative source
https://docs.statsig.com/integrations/mcp/overview ↗Project object catalog, read/write split, write credential requirement, and separation from public Docs MCP
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Authenticated project MCP scope, write behavior, credential model, and docs-server distinction reviewed 2026-07-22
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.
MCP authenticationSource inventory
https://docs.statsig.com/integrations/mcp/manual-setup ↗remote MCP endpoint and authentication prerequisites
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
remote MCP endpoint and authentication prerequisites reviewed from live first-party documentation on 2026-07-22.
Access managementSource inventory
https://docs.statsig.com/access-management/api-keys ↗API key types, CRUD permissions, role inheritance, and audit attribution
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
API key types, CRUD permissions, role inheritance, and audit attribution reviewed from live first-party documentation on 2026-07-22.
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 12, 2026
Targeted first-party access review
Verified fact
Tied to cited first-party evidence reviewed for this profile.
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.