# Create, target or roll out a feature flag or experiment

> Create, target or roll out a feature flag or experiment: 1 companies fully do it, 10 with a limit, 12 carry the tag. Every listing in Product analytics & experimentation with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/product-analytics.flag-experiment-change/
- Markdown: https://www.anchorterminal.com/niches/product-analytics.flag-experiment-change/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/product-analytics.flag-experiment-change/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/product-analytics.flag-experiment-change/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 10 | 12 | 15 | 8 |

## What counts as done

The flag or experiment exists with precisely the requested targeting and split, other fields unchanged, and (for experiments) a running state with a start date, confirmed by a read-back.

Measured, for our own tests: this takes at most 4 calls.

How agents ask for it: create a flag for the new checkout; turn this flag on for users in Canada; roll out to 20 per cent; launch an experiment on iOS and Android; add these emails to the flag

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **LaunchDarkly (Catamorphic, Co. (dba LaunchDarkly))**: create-flag, update-flag-targeting, update-targeting-rules and update-rollout take semantic-patch instructions that change only what is named, and start-experiment-iteration starts an experiment; approvals apply where an environment requires them.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Amplitude (Amplitude, Inc.)**: Management API PATCH takes optional fields including startDate and decision, but targetSegments replaces existing segments and doesn't support cohorts. The MCP no-start issue (acc-18) was closed as resolved internally, not confirmed in docs.
- **Countly (Countly Ltd)**: ab_experiments_create makes a draft with targeting and ab_experiments_start begins it, but remote_config_parameters_update and conditions_update replace the whole resource, so other fields must be resent.
- **Flagsmith (Bullet Train Ltd)**: create_feature, create_segment_override or versioned feature states and update_feature_state cover flags, but tools differ by v2 versioning, update_experiment only edits name and hypothesis, change requests are Enterprise, and a partial PATCH of a multivariate option returned 500 (issue 8901).
- **GrowthBook (GrowthBook, Inc.)**: Feature revisions add, update and publish rules in drafts and experiments start through /start or a status update, but some experiment fields replace the whole stored object, approval rules can hold writes, and the open MCP issue 58 says a plain flag needed a data source.
- **Harness Feature Management & Experimentation (Harness Inc.)**: fme_feature_flag update sends a merge-patch, definitions are created and updated, and segment keys are added by execute actions, but legacy and Harness-native scoping differ per resource, identity writes aren't implemented natively, and change requests can hold writes.
- **Matomo (InnoCraft Limited)**: The AbTesting API manages experiments, but Matomo has no feature flags or percentage rollouts by targeting rule, and the create and start parameters couldn't be read.
- **Mixpanel (Mixpanel, Inc.)**: Create- and Update-Feature-Flag and Update-Experiment (which manages lifecycle) exist, but audience and cohort targeting aren't supported through the MCP, and whether updates are partial isn't stated.
- **Mostly Good Metrics (Mostly Good Metrics)**: create_experiment, update_experiment, start_experiment and stop_experiment cover the lifecycle, but there are no feature flags, targeting rules or rollout percentages, only variants.
- **Optimizely Experimentation (Optimizely North America Inc.)**: Ruleset updates take JSON Patch and an enable endpoint turns a ruleset on, but the MCP's exp_manage_entity_lifecycle asks the person to confirm every live change, so unattended runs need the REST API.
- **PostHog (PostHog Inc. (formerly Hiberly Inc.))**: create-feature-flag, update-feature-flag, release-condition rollout and experiment-launch cover it, but feature-flag-rules-update replaces all rules, and the schema rejected a multi-value equals the UI accepts (acc-06, open).
- **Statsig (Amplitude, Inc.)**: Gates and experiments can be created and started (PUT /experiments/{id}/start), but gate_update and experiment_update replace the whole resource, partial edits need discover_tools, and updates require a confirmation.

- not this job: Fullstory (Fullstory, Inc.): No feature flags or experiments; the MCP only creates drafts of segments, metrics, funnels, journeys and dashboards.
- not this job: Heap (Content Square, Inc.): No feature flags or experiments.
- not this job: OpenPanel (OpenPanel AB): No feature flags or experiments.
- not this job: Pendo (Pendo.io, Inc.): No feature flags, and guide experiments are listed, not created or started, over MCP.
- not this job: RudderStack MCP (RudderStack, Inc.): No feature flags or experiments.
- not this job: Userpilot (Userpilot, Inc.): No feature flags or experiments in the MCP or API reference.
- not this job: Woopra (Woopra, Inc.): No feature flags or experiments.

## What stops agents finishing

- an update replaces the whole resource and resets targeting
- the MCP schema rejects targeting the UI accepts
- starting an experiment only possible in the UI
- flag creation demands an experiment data source
- writes held for human approval or change requests

## Around it

Before: code.add-flag-check. After: product-analytics.experiment-readout.

## Where this comes from

Weight 15 of 100 in Product analytics & experimentation: 8 of 55 account links, nearly all GitHub issues about writes that silently did the wrong thing

As data: https://www.anchorterminal.com/api/v1/use-cases/product-analytics.flag-experiment-change.json, or the MCP tool get_use_case with id product-analytics.flag-experiment-change. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
