flAPI speaks MCP 2026-07-28 — and your slow queries finally stopped timing out
There's a moment every team hits when they wire an AI agent up to their real data warehouse. The demo works. The "show me last quarter's revenue by region" query works. And then someone asks for something that scans a few hundred million rows across BigQuery and SAP, the query takes ninety seconds, and the whole thing falls over — not because the query failed, but because something in the middle gave up waiting. A reverse proxy. A load balancer. The client's own timeout. The query was fine. The connection wasn't.
flAPI v26.08.31 is largely about that ninety-second gap — and about a bigger shift underneath it: MCP, the protocol AI clients use to call your tools, quietly stopped being a session protocol. Both of those changes landed in this release, and neither one breaks a single existing client.
If you're new here: flAPI turns SQL templates and a little YAML into REST APIs and MCP tools at the same time. You write a query; flAPI gives you an endpoint your services can call and a tool your AI agents can call, from the same file. It's a single C++ binary with DuckDB inside, so those tools reach BigQuery, Postgres, Iceberg, S3, SAP and 50-odd other sources.