Welcome
Public documentation for the AKKO bricks, starting with akko-mcp-trino.
AKKO builds governed-access bricks between AI agents and enterprise data. Each brick installs on its own, on the engines and identity providers you already run, and proves itself on its own. This documentation covers what is public.
The bricks
akko-mcp-trino
A governed MCP server for Trino. Every tool call carries the user's identity; the engine decides.
How it works
Follow one question end to end, from the person's identity down to Trino, then to the audit line.
To understand akko-mcp-trino, start with How it works. The overview then gives the guarantees, the proofs and the open source core.
How to read this documentation
Each page answers the question in its title first, then gives prerequisites, configuration and what has been proven. The proof scripts, which can be replayed, live in the platform repository because they know its cluster; when a page says “proven”, it describes what the proof checks and its result.
Going further
The blog tells the architecture choices and what the proofs taught us. For a question about a brick or the platform, write to us.