Integration · Kameleoon
Kameleoon's MCP focuses on the implementation workflow. Pull raw variation code (JS or CSS) from a winning experiment and convert it to a production-ready React component the team ships behind a flag.
Seven specialized tools. The MCP is scoped to the convert-and-promote flow rather than broad CRUD, which is a deliberate design choice: agents work best with a small, sharp toolset for a specific job, and Kameleoon already has a strong dashboard for the rest.
What you can do via MCP
“List my Kameleoon feature flags.”
Returns the flag list scoped to the user's Kameleoon site, including current state and last evaluation timestamp.
“Show me the winner data for experiment 149640.”
Pulls experiment results, identifies the winning variation, and surfaces the lift, confidence, and segment-level effects.
“Pull the variation code for experiment 149640 and convert it to React components.”
Reads the raw JS/CSS variation, refactors it into a typed React component with proper props, and proposes the integration site in the codebase.
“Create a feature flag 'pbx-experiment-373001-winner' and gate the converted code behind it.”
Creates the flag, wires the converted component to evaluate it, and stages a PR that ships the new code path off by default.
“Enable the new-search flag in production.”
Toggles the production environment for the named flag and confirms the change took effect.
The convert-winning-variation flow. The agent reads the raw variation code from Kameleoon, then proposes the React component. The same prompt also stages the flag for the rollout.
# Kameleoon MCP, hosted, OAuth via mcp-remote proxy
# Connect: https://mcp.kameleoon.com/mcp
mcp.kameleoon.get_variation_code({
experiment_id: 149640,
variation_id: 373001
})
// Returns raw JS + CSS
mcp.kameleoon.create_feature_flag({
key: "pbx-experiment-373001-winner",
description: "Promoted from winning variation"
})
// Agent then refactors variation code into a React
// component gated by the new flag, opens PR.MCP integration
Visual demonstration
Primary metric: signup_completed
| Variant | Metric | Lift | 95% CI | p |
|---|---|---|---|---|
| Controlcontrol | 6.10% | baseline | — | — |
| Variation 373001 | 7.04% | +15.41% | [7.80, 23.00] | 0.001 |
Significant winner. Agent's next step: pull variation_id 373001 code and convert to a React component gated behind a new flag.
CLI alternative
Kameleoon does not ship a first-party CLI. The hosted MCP plus the standard Kameleoon REST API cover programmatic access; for AI workflows the MCP is the right interface, and the dashboard handles the broader CRUD work the seven-tool MCP intentionally does not cover.
Pairs with these skills
This integration pairs with the forthcoming experiment-design, feature-flagging skills. The skill landing pages and SKILL.md sources land in subsequent dispatches; cross-link hyperlinks are added when the skill pages ship.
Cost considerations
No per-call cost; usage is bounded by the plan tier you already pay for. Lean on the MCP for exploratory work the way you would lean on the platform UI: the marginal cost of an extra call is zero, and the agent reads or writes the same data your team already has access to.
Kameleoon plan covers MCP usage. The MCP is specialized for variation-to-production-code workflows rather than broad CRUD.