PRACTICAL FIELD GUIDE
Boolean fields: agree on the stored representation
MCPBackend's boolean schema type uses SQLite integer storage, so clients need a consistent representation at the API boundary. Verify accepted values instead of relying on language-specific truthiness.
MCPBackend editorial team · · Examples are illustrative
Put it into practice
- Read the generated schema and inspect how boolean values are returned.
- Normalize form input to the supported representation before submission.
- Test false, missing and null values separately, especially when using defaults.
What this looks like
ILLUSTRATIVE EXAMPLE
A checkbox sends the string false, which application code later treats as truthy. Consistent conversion prevents that mismatch.
A boundary to keep clear
Do not use a broad Boolean conversion on untrusted strings. A nonempty string is not the same as the intended true value.
MCPBackend context
MCPBackend stores each project's data in SQLite and exposes supported tables through generated REST endpoints. Use the schema tools and dashboard for supported changes. The design examples here are patterns to adapt, not claims that the API exposes every SQLite feature or arbitrary SQL.
Take the next step
Inspect the current project contract, try the change with disposable data, and verify the result through the same credentials your app will use. Record the expected response and one denied-access case before release.
Sources and further reading
These references explain the underlying protocols and design principles. For supported MCPBackend operations and exact request shapes, inspect your project’s generated API contract.