Bricks that install on their own, on what you already have.

A brick installs on an existing Trino, directory and catalogue, and asks for neither the AKKO platform nor another engine. It comes with its documentation and its proofs.

Available · 0.7.2 · Apache 2.0

akko-mcp-trino

The governed MCP server for Trino. Every tool call carries the user's identity; Trino and its policy engine decide. Its open source core reads by default under each user's identity, or under a single identity the administrator names, read-only, bounds on every call and one audit line per call. AKKO and ARCHE add agent and access management, other ways to carry the user's identity, an audit linked to the engine's log and the business context of the catalogue.

Documentation Source code PyPI

$ pip install akko-mcp-trino

1identity per call, the person's
0write let through
3transports: streamable-http, sse, stdio
8tools in the open core

How it works

The adversarial proof, as it prints

tests/proofs/akko-mcp-trino-adversarial-live-proof.sh

== 3. Verifications ==-- A. concurrence (streamable-http) : 2 utilisateurs x 4 sessions x 3 appelsOK    appels aboutis24OK    alice : 12 reponses en clair12OK    carol : 12 reponses masquees12OK    reponses croisees (fuite)0-- B. adverseOK    DROP refuseRead-only modeOK    WITH qui enveloppe un DELETE refuseRead-only modeOK    EXPLAIN ANALYZE d'une ecriture refuseRead-only modeOK    carol : TABLE(system.query) refuse (sans masque)Read-only modeOK    injection dans tableTrueOK    jeton signe par une autre cle401/unauthenticatedOK    jeton expire401/unauthenticated== PREUVE ADVERSE OK ==

Soon

akko-lab

The platform lab: JupyterHub notebooks, code environments and model tracking, with data access governed like everything else.

Planned

Identity broker

Carrying the person's identity across directories and engines: a Keycloak user is recognised by a Kerberised Trino or by Ranger, without a shared account.

Planned

Policy sync

A classification set in the catalogue (OpenMetadata) becomes a policy in Ranger or OPA, and a refusal in the engine.

Planned

Benchmark

Two accounts, two answers, on your engines: the proof that governance holds, replayable by a third party.

Licences

What is open, and under which licence.

Published bricks

Apache 2.0. The core of akko-mcp-trino is published; akko-lab will follow. Code on GitHub, package on PyPI.

Upstream components

Trino, Iceberg, OpenMetadata, Airflow, Spark, Superset, JupyterHub, MLflow, Keycloak, OPA are open source projects that AKKO installs and wires without forking them.

The platform and the control plane

The installation documentation is public.

Is the AKKO platform open source?: No. Only the core of akko-mcp-trino is under Apache 2.0, because governed access for AI agents is useful to the whole Trino ecosystem; its advanced features are delivered in AKKO and ARCHE.
Can I use a brick without AKKO?: Yes. A brick installs on its own, on your Trino, your directory and your catalogue, and never requires the platform.

Try a brick, or talk to us.

Install akko-mcp-trino with pip install akko-mcp-trino, and tell us what is missing.

Read the documentation Write to us