One product. Two capabilities. Meridian is the Kubernetes-native control plane that manages your Trino clusters — and the MCP server that lets AI agents operate them.
Pre-provisioned clusters sit idle and are claimed instantly. No 30–90 second provisioning delay when a job needs a cluster.
19 tools for Claude Code, Claude Desktop, Cursor, and any MCP client. Follows the latest MCP spec (2026-07-28): one stateless /mcp endpoint that scales to many replicas. Older clients keep working.
Three controllers, three CRDs, one Helm chart. Runs in any Kubernetes cluster. No external dependencies, no database, no sidecar.
Six mTLS-authenticated endpoints: list and filter clusters, get a cluster, list pools, scale replicas, reserve and release — all machine-to-machine.
ClusterPoolAutoscaler watches reservation utilization and scales the pool up or down automatically with hysteresis.
Same clientId + reservationId always returns the same cluster. Crashed clients are handled automatically: reservations expire after a configurable TTL.
The MCP server requires a token and runs queries read-only. Tools that change clusters stay off until you enable them. The REST API uses mTLS, and pods run as non-root.
Rotate catalog credentials from Kubernetes Secrets, HashiCorp Vault, or AWS Secrets Manager. The catalog is swapped on the live cluster, with no restart.
Every pull request installs the last release on Kubernetes, upgrades it, and runs 11 end-to-end scenarios with real Trino: queries, reservations, crashes, rotation, and rolling restarts.
Reserve a fresh cluster per test run, release on completion. No shared state, no flaky tests from cluster contention.
GitHub Actions · JenkinsManage cluster lifecycle as a DAG task. Reserve before the job, release after — same as any other resource.
Airflow · Dagster · PrefectExpose cluster provisioning to app developers through a form. No kubectl access required.
Backstage · CortexDeclare cluster pools as versioned resources alongside the rest of your infrastructure.
Terraform · Pulumi--enable-tools
The most requested infrastructure feature in the Trino project. Meridian ships three controllers and three CRDs, fully open source.
Meridian ships 19 MCP tools covering the full operational surface — cluster lifecycle, catalogs, credentials, queries, and audit.
MCP server for AI agents, Claude Desktop, and CI/CD pipelines.
Kubernetes operator — manages the full Trino cluster lifecycle.
Apache 2.0 · Self-hosted · No SaaS · No lock-in