GrowthBook MCP

Because it is a thin bridge, not an endpoint wrapper. GrowthBook describes the server as loading Agent Skills and making authenticated calls to its REST API. Two tools list and read those skills; the other two are authenticated GET and mutating passthroughs to the API. Version 2.x deliberately removed the old per-endpoint tools.

No, and GrowthBook says so plainly: the API tools are authenticated passthroughs that do not validate payloads. It places the guardrails in the skills instead, which encode workflows like draft then review then publish and safe rollouts. An agent that skips the skills is calling your REST API unguarded.

Not through a documented read-only mode. growthbook_api_write performs POST, PUT, PATCH and DELETE against the REST API, and there is no separate read-only endpoint. GrowthBook does document a capability-only mode at slash mcp slash api that drops the skills, but that exposes both read and write tools, not read alone.

Teams that supply their own workflows. Connecting to slash mcp slash api instead of slash mcp exposes only growthbook_api_read and growthbook_api_write, without the bundled skills. GrowthBook suggests it when your client or team already has its own guardrails, so you are not loading GrowthBook's opinions about how to sequence changes.

No. GrowthBook documents that Cloud users sign in with OAuth in the browser with no API key in the MCP config, and we confirmed the server issues an OAuth challenge naming api.growthbook.io as its authorization server. The advertised scopes are openid, profile, email and offline_access.

Version 2.x removed them. GrowthBook documents that the old per-endpoint tools such as create_feature_flag and get_experiments are gone, replaced by the skill loader plus the API read and write tools. Cloud clients should point at mcp.growthbook.io slash mcp, and local installs should upgrade to the latest package.