Skip to main content
The MCP Server and this plugin load the same playbooks. Use this page only if you want those playbooks installed locally — slash commands, no MCP process. On GrowthBook Cloud, most hosts should use the hosted MCP endpoint instead. The plugin works in agents that follow the Agent Skills standard and can run shell commands: Claude Code, Cursor, Codex, and others. It calls the GrowthBook REST API through a small bundled helper.
Open sourceThe playbooks live at github.com/growthbook/skills. The MCP server bundles that same repo at build time.

​
Prerequisites

  • A GrowthBook account: GrowthBook Cloud or a self-hosted instance.
  • A Personal Access Token (PAT): create one at Account → Personal Access Tokens. The token is tied to your GrowthBook user, so flags and experiments the plugin creates are attributed to you.
  • Node.js 18+: check with node -v. Many agents already run on it.

​
Install

Add the marketplace, then install the plugin:

​
Configure credentials

Run the setup skill and follow the prompts:
It asks for your PAT or API key (and, for self-hosted, your API URL), validates them against the live API, and writes ~/.config/growthbook/.env with chmod 600. Every other skill reads that file automatically.
Prefer environment variables?The helper reads environment variables first and only falls back to the file. Handy for CI:
Then ask your agent to list your feature flags. If the credentials are wrong, the error points you back to /growthbook:gb-setup.

​
What you can do

The plugin covers four domains. Describe the task in natural language, or use a /growthbook:… slash command in Claude Code. The agent picks the matching workflow. The live workflow list is in the skills README. MCP users get the same list from growthbook_list_skills. Guardrails are in the playbooks, not in this page: draft → review → publish, two-step deletes, and read-only workflows that never write. See Publishing & approval flows.

​
Next steps

Join our community Slack for additional help, tips, and announcements