A Model Context Protocol (MCP) connector for Trino, enabling seamless integration between MCP-compliant services and Trino query engine
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-alaturqua-mcp-trino-python","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
[](https://mseep.ai/app/alaturqua-mcp-trino-python) # MCP Trino Server [](https://smithery.ai/server/@alaturqua/mcp-trino-python) [](https://www.python.org/downloads/) [](https://code.visualstudio.com/) [](https://github.com/alaturqua/mcp-trino-python/pkgs/container/mcp-trino-python) [](https://opensource.org/licenses/Apache-2.0) The MCP Trino Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that provides seamless integration with Trino and Iceberg, enabling advanced data exploration, querying, and table maintenance capabilities through a standard interface. ## Use Cases - Interactive data exploration and analysis in Trino - Automated Iceberg table maintenance and optimization - Building AI-powered tools that interact with Trino databases - Executing and managing SQL queries with proper result formatting ## Prerequisites 1. A running Trino server (or Docker Compose for local development) 2. Python 3.12 or higher 3. Docker (optional, for containerized deployment) ## Quick Start ### 1. Clone the Repository ```bash git clone https://github.com/alaturqua/mcp-trino-python.git cd mcp-trino-python ``` ### 2. Create Environment File Create a `.env` file in the root directory: ```bash TRINO_HOST=localhost TRINO_PORT=8080 TRINO_USER=trino TRINO_CATALOG=tpch TRINO_SCHEMA=tiny ``` ### 3. Run Trino Locally (Optional) ```…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.