A
securityA
licenseA
qualityProvides AI models with structured access to Trino's distributed SQL query engine, enabling LLMs to directly query and analyze data stored in Trino databases.
Last updated -
3
1
Python
MIT License
Trino (formerly PrestoSQL) is an open-source distributed SQL query engine for big data analytics that allows querying data where it lives across multiple data sources.
Why this server?
Provides structured access to Trino's distributed SQL query engine, enabling execution of SQL queries, inspection of database schemas and tables, and running complex analytical queries against data in Trino catalogs and schemas.
Why this server?
Enables SQL access to Trino distributed query engine data.
Why this server?
Enables read-only access to Trino (formerly PrestoSQL) data through SQL interfaces.
Why this server?
Enables querying of Trino distributed SQL query engine data through relational SQL models.
Why this server?
Allows SQL-based access to Trino (formerly PrestoSQL) distributed query engine, providing queries against various data sources.
Why this server?
Enables SQL-based access to Trino (formerly PrestoSQL) distributed query engine data sources.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver integration.
Why this server?
Allows retrieval of SAS Data Sets containing Trino data via SQL queries.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Trino data.
Why this server?
Enables access to Trino (formerly PrestoSQL) distributed query engine in a read-only capacity.
Why this server?
Provides SQL query capabilities for Trino distributed SQL query engine.
Why this server?
Allows querying data sources connected through Trino using SQL.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Allows access to Trino (formerly PrestoSQL) distributed SQL query engine data.
Why this server?
Enables access to Trino distributed SQL query engine data through SQL queries.
Why this server?
Allows reading data through the Trino distributed SQL query engine.
Why this server?
Allows querying Trino distributed SQL query engine data by representing it as relational tables, supporting table discovery, column information retrieval, and SQL query execution.
Why this server?
Enables querying Trino distributed SQL query engine data through SQL.
Why this server?
Provides SQL querying of Trino distributed SQL engine data
Why this server?
Listed as a supported data source that can be integrated with the MCP server for data access.
Why this server?
Enables querying and retrieval of data from Trino distributed SQL query engine through SQL-based tools for listing tables, retrieving column information, and executing SELECT queries.
Why this server?
Listed as a supported data source for querying Trino (formerly PrestoSQL) distributed query engine.
Why this server?
Provides SQL access to Trino (formerly PrestoSQL) distributed query engine data.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver, enabling data querying capabilities.
Why this server?
Listed as a supported data source for integration, allowing access to Trino data through the MCP server.
Why this server?
Enables querying of Trino data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver, allowing for data retrieval from Trino SQL query engine.
Why this server?
Allows retrieval of data through Trino distributed SQL query engine via natural language queries.
Why this server?
Allows access to Trino SQL query engine data by exposing it as relational SQL tables accessible through the MCP server.
Why this server?
Enables SQL-based access to Trino distributed SQL query engine.
Why this server?
Enables reading Trino (formerly PrestoSQL) distributed query engine data through SQL interfaces, allowing natural language querying of big data.
Why this server?
Enables SQL query capabilities for data accessible through Trino distributed query engine.
Why this server?
Enables access to Trino SQL query engine data by exposing it as relational SQL models through the CData JDBC driver.
Why this server?
Listed as a supported data source for integration, allowing access to Trino distributed SQL query engine.
Why this server?
Provides read-only access to Trino data by exposing tables as relational SQL models, allowing retrieval of live data through simple MCP queries.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Enables querying Trino data sources by exposing them as relational SQL models that can be accessed through natural language queries.
Why this server?
Provides querying of Trino distributed SQL query engine through SQL interfaces.
Why this server?
Allows querying data through Trino distributed SQL query engine.
Why this server?
Allows SQL-like access to Trino (formerly PrestoSQL) distributed query engine data.
Why this server?
Provides read-only SQL-based access to data through Trino (formerly PrestoSQL) distributed query engine.
Why this server?
Enables SQL queries against Trino (formerly PrestoSQL) distributed query engines, accessing data across heterogeneous sources.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver framework.
Why this server?
Allows querying of data through Trino distributed SQL query engine.
Why this server?
Listed as a supported data source that can be accessed through the MCP server.
Why this server?
Provides read-only access to Trino data through SQL models, allowing queries of Trino data through natural language requests.
Why this server?
Enables SQL access to data sources connected to Trino (formerly PrestoSQL) distributed query engine.
Why this server?
Enables querying Trino distributed SQL query engine data.
Why this server?
Listed as a supported data source for integration, enabling access to Trino SQL query engine data through the CData JDBC Driver.
Why this server?
Listed as a supported data source that can be queried through the MCP server.
Why this server?
Enables querying Trino data through SQL, allowing retrieval of distributed query engine information through natural language questions.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for retrieving data.
Why this server?
Enables SQL-based access to Trino distributed query engine data, supporting querying of connected data sources.
Why this server?
Enables querying of Trino (formerly PrestoSQL) distributed SQL query engine data sources.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for querying Trino data.
Why this server?
Enables querying Trino (formerly PrestoSQL) distributed SQL query engine data sources through a SQL interface.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Provides SQL-based access to Trino distributed query engine and its data sources.
Why this server?
Provides SQL interface for accessing Trino distributed query engine data.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Trino data.
Why this server?
Enables SQL-based access to Trino (formerly PrestoSQL) distributed query engine data sources.
Why this server?
Enables querying Trino (formerly PrestoSQL) distributed SQL query engine data.
Why this server?
Allows querying Trino distributed SQL query engine data through SQL models.
Why this server?
Listed as a supported data source that can be accessed through CData JDBC Driver and exposed via the MCP server.
Why this server?
Enables querying data across multiple data sources using Trino (formerly PrestoSQL).
Why this server?
Allows querying Trino data through natural language questions rather than SQL.
Why this server?
Included in the list of supported sources for data retrieval through the MCP server.
Why this server?
Provides read-only access to Trino (formerly PrestoSQL) distributed query engine data, allowing retrieval of information across data sources through natural language queries.
Why this server?
Provides access to Trino (formerly PrestoSQL) distributed SQL query engine data.
Why this server?
Provides SQL interface for querying Trino (formerly PrestoSQL) distributed query engines.
Why this server?
Provides SQL-based access to Trino distributed SQL query engine data.
Why this server?
Enables read-only access to Trino (formerly PrestoSQL) distributed query engine data, allowing SQL queries across diverse data sources.
Why this server?
Provides seamless integration with Trino for interactive data exploration, executing SQL queries, catalog/schema navigation, and retrieving query results in formatted outputs.
Why this server?
Allows users to list tables, read table contents, and execute arbitrary SQL queries against a Trino database through an MCP server
Why this server?
Allows AI assistants to execute SQL queries against a Trino distributed SQL query engine, with support for catalog/schema/table discovery and schema inspection.