Bug Report: FCRM MCP > stores tracking settings as strings causing a false “tracking disabled” warning

Description:
Environment:

• FluentCRM 3.1.10
• Campaign created through the FluentCRM MCP
• Open and click tracking enabled

When a campaign is created through the MCP, the campaign settings are stored as:

open_tracker: "yes"
click_tracker: "yes"

These are strings rather than JSON booleans. The campaign report interface appears to require the strict boolean value true when determining whether tracking is enabled.

As a result, the report incorrectly states that open and click tracking were disabled for the campaign and hides or disables the View, Click and Unopened filters. However, tracking itself remains operational and open and click events continue to be recorded.

Steps to reproduce:

1. Create a campaign through the MCP with open and click tracking enabled.
2. Send the campaign and open its report.
3. Observe the “tracking disabled” warning and the unavailable report filters.
4. Inspect the campaign settings and confirm that both tracker values are stored as the string "yes".
5. Change only those two values to the boolean true through the REST API.
6. Reload the report.

Actual result:
The MCP stores string values. The report treats tracking as disabled, despite tracking events being recorded.

Expected result:
The MCP should store boolean values, consistently with the format expected by FluentCRM, or FluentCRM should normalize supported string values before evaluating them.

Verified workaround:
Changing only open_tracker and click_tracker from "yes" to true removes the warning and restores the report filters. It does not resend the campaign or alter its recipients, sent emails, opens, clicks or existing metrics.

I think there’s a need for updating the MCP schema or serializer to send JSON booleans for these fields. As an additional compatibility measure, FluentCRM could normalize "yes"/"no" values when loading campaign settings.