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, Cursor, and any MCP client. Reserve clusters, add catalogs, run queries — all through natural language.
Three controllers, three CRDs. Runs in any Kubernetes cluster. No external dependencies, no database, no sidecar.
Add and remove catalogs at runtime via Trino's catalog.management=dynamic. No cluster restart.
ClusterPoolAutoscaler watches reservation utilization and scales the pool up or down automatically with hysteresis.
Same clientId + reservationId always returns the same cluster. Optimistic concurrency handles races safely.
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 · PulumiThe 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