Why GrowthBook’s MCP server is just the interface

GrowthBook rebuilt its MCP server from a large collection of product-specific tools into a thin adapter that routes agents to a typed REST API for product capabilities and reusable skills for workflow guidance, reducing maintenance duplication across its API, CLI, MCP clients, and in-app assistant. The API supports operations involving feature flags, experiments, metrics, and configuration, while skills instruct agents on how to investigate context, follow experimentation procedures, identify assumptions, and return evidence for human review; permissions, validation, approval policies, review states, and audit logs remain the product-layer controls rather than security functions of the skills themselves. GrowthBook also uses experiment history and curated Learnings as context, enabling agents to generate and develop test ideas grounded in prior results, while requiring people to select proposals and approve consequential actions such as customer exposure changes. The company argues that autonomy should be determined by risk, reversibility, and organizational controls rather than simply whether an operation is a read or write, and that trust should be built progressively through inspectable outputs, limited credentials, sandbox work, and reviewable changes. By treating MCP as one interface among many rather than the core product, GrowthBook aims to support engineers, product managers, analysts, and growth teams across editors, terminals, chat clients, and its application while preserving a shared experimentation model and governance process.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.