Back to MCP Directory
Trino
Model Context Protocol moderate risk

Trino

This MCP server allows listing and querying Trino tables, executing SQL queries, and reading table contents, configured via environment variables.

Connections & Capabilities

Connects To

PostgreSQL

Capabilities

readexec

Quickstart

Config

{
  "mcpServers": {
    "trino": {
      "command": "uv",
      "args": [
        "--directory", 
        "<path_to_mcp_server_trino>",
        "run",
        "mcp_server_trino"
      ],
      "env": {
        "TRINO_HOST": "<host>",
        "TRINO_PORT": "<port>",
        "TRINO_USER": "<user>",
        "TRINO_PASSWORD": "<password>",
        "TRINO_CATALOG": "<catalog>",
        "TRINO_SCHEMA": "<schema>"
      }
    }
  }
}

Exposed MCP Tools (3)

safe
list_tables

Lists available tables in the configured Trino catalog and schema.

Read-only operation; no data modification.

safe
read_table

Reads the contents of a specified Trino table.

Read-only operation; no data modification.

high
execute_sql

Executes an arbitrary SQL query against the Trino database.

Allows arbitrary SQL execution, potentially leading to data modification or leakage.

Safety Assessment

This server is relatively safe for read-only operations and listing tables. However, executing arbitrary SQL queries introduces significant risk, especially if proper input validation and resource controls are not implemented. Secure handling of environment variables is crucial.

  • Trino connection details are configured via environment variables.
  • Access is limited to the specified catalog and schema.
  • Password can be optional depending on Trino authentication setup.
  • MCP provides a layer of abstraction, potentially limiting direct access to Trino.
  • Executes arbitrary SQL queries, posing a risk of data modification or leakage.
  • Relies on environment variables for secrets, which can be exposed if not handled correctly.
  • Lack of explicit input validation on SQL queries could lead to injection vulnerabilities.
  • No mention of resource limits or query timeouts, potentially leading to denial-of-service.