MCP For Claude Marketplace
Deterministic Feature Flag Evaluator

Deterministic Feature Flag Evaluator MCP Connector for Claude

A+

Evaluate feature flags using consistent, hash-based logic to prevent session flicker.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner
More Details Connect to Claude

The Deterministic Feature Flag Evaluator provides a reliable way to manage feature rollouts without the risk of inconsistent user experiences. By utilizing CRC32 hashing on the combination of a flag key and a user ID, it ensures that a user's assignment to a feature remains stable across different sessions and agents. This MCP server allows you to use evaluate_flag to check if a specific user meets rollout criteria, verify_distribution to validate the uniformity of your percentage-based rollouts, and get_flag_config to retrieve existing rule definitions from the registry. It is an essential tool for maintaining feature consistency in multi-agent environments like Cursor, VS Code, and Claude Desktop.

feature-flagsdeterministichashingrollouttesting

3 tools expose this connector's capabilities to your AI agent.

get_flag_config

Retrieves the configuration for a given flag key

verify_distribution

Verifies if the flag distribution is uniform across a sample size

evaluate_flag

Evaluates if a feature flag is enabled for a specific user

See how to talk to your AI agent using Deterministic Feature Flag Evaluator.

Check if user 'user_123' is enabled for the 'new_ui_v2' flag with a 50% rollout.

The evaluation for user 'user_12im' on flag 'new_ui_v2' resulted in: isEnabled: true, evaluationReason: PERCENTAGE, hashValue: 42.

Retrieve the configuration for the 'beta_search' flag.

The configuration for 'beta_search' was found: configExists: true, rules: {"percentageRollout": 25, "allowedIds": ["admin_01"]}.

Verify if a 10% rollout for 'dark_mode' is uniform using a sample of 1000 users.

The distribution test completed: observedPercentage: 10.2, deviationFromExpected: 0.2, isWithinTolerance: true.

The system uses CRC32 hashing of the `flagKey` and `userId`. Since these inputs are immutable for a specific user and flag, the resulting hash value remains constant, ensuring the feature state does not change between sessions.

Related Connectors

Statsig

Statsig MCP

12 tools Official

Manage feature flags, dynamic configs, and experiments. Evaluate gates and log events directly from your AI agent.

A+ View details →
Unleash (Feature Toggles)

Unleash (Feature Toggles) MCP

11 tools Official

Manage feature flags, strategies, and environments via Unleash — evaluate toggles, list projects, and monitor metrics directly from your AI agent.

A+ View details →
Feathery

Feathery MCP

11 tools Official

Automate forms and user workflows via Feathery — manage users, retrieve form data, and monitor connector logs directly through your AI agent.

A+ View details →
Sumo Logic

Sumo Logic MCP

9 tools Official

Connect your AI to Sumo Logic. Orchestrate log searches, monitor active collectors, and analyze system events efficiently.

A+ View details →