Trino MCP — OAuth 2.1 + Query CLI for Data Warehouses

Practical Notes

• Quant: the CLI supports catalogs/schemas/tables/describe/explain commands—use it as a deterministic health check for agent tooling.
• Quant: for production, adopt OAuth so every query is attributable to a user identity instead of a shared service token.

Rollout pattern

• Use CLI mode to validate baseline connectivity, then connect an MCP client for natural-language workflows.
• Create a least-privilege Trino user for agent workflows; keep admin capabilities out-of-band.
• Enable OAuth when you move beyond a single-user laptop setup to shared deployments.

Watchouts

A powerful query tool can become an exfiltration path. Apply catalog/schema allowlists, result-size limits, and audit logging before broad rollout.

FAQ

Q: Is the CLI required? A: No, but it is a great verification tool. Use the CLI for deterministic smoke tests before LLM-driven queries.

Q: What does OAuth buy me? A: User-level attribution and safer shared deployments, instead of one shared token for everyone.

Q: How do I start safely? A: Use a staging Trino environment, restrict catalogs, and keep query limits small until you understand agent behavior.