...and what about AI?

FLXBL, being a Backend-as-a-Service system does not contain any AI features, and that is by design.
Our product delivers predictable, complex engineering features, and we don't see any kind of AI features as a fit in the core of the product itself.
However, we are definitely aware of AI usage and many different use cases where AI and AI-assisted coding can be extremely helpful.
That's why our CLI is what we like to call AI friendly.

The CLI is built to be driven by agents. Every mutating command follows the same contract:

--json — every command emits a stable JSON envelope on stdout. Errors emit { code, message, details?, exitCode } to stderr.

--stdin — any command that takes a --data, --file, or --items argument also accepts the payload on stdin, so agents don't need a filesystem:

echo '{"name":"Widget","price":9.99}' | flxbl entity create Product --stdin --json

--dry-run — supported by all mutating commands (entity, relationship, role, webhook, schema create|delete|migrate|validate, identity update, team invite|remove). Prints the request that would be sent (method, path, body) and exits 0 without calling the API. No backend support required.

flxbl entity create Product --data '{"name":"X"}' --dry-run --json

There's a detailed article on the reasoning behind the logic of CLI and the reasons of retiring the MCP server in favour of CLI.