Integration · Flagsmith

Open-source feature flags with change request workflows.

Flagsmith is the open-source feature flag platform with strong governance via change request workflows. The MCP routes flag changes through the same approval flow human edits use.

Hosted MCP via Gram at app.getgram.ai. Self-hosted Flagsmith works too, with a custom server URL header. SOC 2 Type 2, HIPAA, and FedRAMP support make Flagsmith the right pick for regulated environments.

Official MCPSelf-host or cloud. Apache 2.0 platform.

What you can do via MCP

Example prompts the agent runs.

  • “List all feature flags in the production environment.”

    Returns the flag list scoped to production with current state, owner, and last change author.

  • “Create a flag 'new-checkout-flow' with default off.”

    Creates the flag, sets the default off, and surfaces the SDK snippet for the client integration.

  • “Submit a change request to enable pricing-banner in production.”

    Opens a Flagsmith change request for the production toggle. The change does not apply until human reviewers approve it.

  • “Find stale flags that haven't been evaluated in 90 days.”

    Pulls flag list, filters by last evaluation timestamp, and surfaces a cleanup plan grouped by owner.

  • “Add the user 'alice@example.com' to the beta-testers segment.”

    Adds the identity to the segment, confirms the change, and notes the flags affected by the new membership.

Flagsmith · MCP

Submitting a change request through the MCP. The change does not apply until reviewers approve, which keeps the audit trail intact for regulated environments.

Flagsmith MCP
docs
# Flagsmith MCP, hosted via Gram
# Connect: https://app.getgram.ai/mcp/flagsmith-mcp
# Header: Authorization: Api-Key ser.abc123...
# Self-hosted: Mcp-Flagsmith-Server-Url: <your-instance>

mcp.flagsmith.create_change_request({
  feature: "pricing-banner",
  environment: "production",
  proposed_state: { enabled: true },
  description: "Enable pricing banner per growth team brief"
})

# Returns change_request_id; status: PENDING_APPROVAL
# Auto-applies when reviewers approve.
One command sample showing how the agent talks to Flagsmith. The MCP exposes the platform's primitives as tools; the agent translates the prompt into the right call.

MCP integration

Flagsmith MCP server.

Server
https://app.getgram.ai/mcp/flagsmith-mcp
Auth
Organisation API key (Api-Key ser.abc123... format)
Hosting
Hosted via Gram (default), or self-hosted with the Mcp-Flagsmith-Server-Url header
  • Change request workflows route AI flag changes through human approval
  • SOC 2 Type 2, HIPAA, FedRAMP support for regulated environments
  • Self-hosted Flagsmith works via header override; cloud via the default Gram URL
  • Open source under the Flagsmith Standard License

Flagsmith MCP docs

Visual demonstration

What this looks like in practice.

Flagsmith/Feature flag
Release

pricing-banner

Holiday-season pricing banner promotion

Environment

production

Off0% rollout

Targeting rules

  • segment IS beta-testers ENABLE 100%
  • Pending change request: enable in production (awaiting approval)
A flag with a pending change request. The agent submitted the change; the production toggle stays off until a reviewer approves.
Flagsmith· Stale flag audit
2 stale of 3

  • old-search-banner

    Stale

    Last evaluated 104 days ago · @growth

    Banner removed last quarter; flag still active

    Remove

  • experimental-onboarding

    Stale

    Last evaluated 67 days ago · @onboarding

    Decided experiment, ship variant on; flag still gating

    Remove

  • pricing-banner

    Active

    Last evaluated 12 minutes ago · @growth

    Active rollout (pending change request)

    Keep
Stale flag audit run by the agent. Cleanup actions still flow through the change request workflow, not direct edits.

CLI alternative

REST API plus MCP.

Flagsmith ships a comprehensive REST API for non-agent integration. The MCP is the AI-native interface; the REST API covers CI integration, scripted reporting, and SDK initialization. Most teams use both: MCP for agent-driven flag work that flows through change requests, REST for build-time and ops automation.

Pairs with these skills

The PM-experimentation skill suite.

This integration pairs with the forthcoming feature-flagging skill. The skill landing pages and SKILL.md sources land in subsequent dispatches; cross-link hyperlinks are added when the skill pages ship.

Continue reading.