MCP Server Feature Flag Validation Bug

[sreuter]

MCP Server Feature Flag Validation Bug

Issue: The MCP server has incorrect validation when adding or editing feature flags with filters using the "equals" operator.

Current behavior: When attempting to update a feature flag with a property filter that uses operator: "exact" with multiple values (as an array), the MCP server throws a validation error: operator "exact" is not valid for value type "array"

Expected behavior: PostHog's API and UI support using the "equals" operator with multiple values. The MCP server should accept this configuration as valid.

Example:
Attempting to update a feature flag to match users with emails like user1@example.com, user2@example.com, and user3@example.com using:

{
  "filters": {
    "groups": [{
      "properties": [{
        "key": "email",
        "value": ["user1@example.com", "user2@example.com", "user3@example.com"],
        "operator": "exact"
      }],
      "rollout_percentage": 100
    }]
  }
}

This is rejected by the MCP server's validation, even though it's a valid PostHog feature flag configuration.

Impact: Users cannot add or edit feature flags with multiple values using the "equals" operator through the MCP server, forcing them to use the UI instead.