MCP Trino Python

MCP server for Presto/Trino SQL queries with Cursor integration, featuring native MCP protocol support.

Features

• Connect to Presto/Trino databases
• Execute SQL queries and retrieve results
• Streaming data with pandas DataFrame support
• Run via npx without global installation
• Native MCP protocol for direct Cursor integration

Requirements

• Python 3.8+
• uv package manager
• Node.js 12+ (for npx usage)

Installation

1. Clone the repository:

git clone <repository-url>
cd mcp-trino-python

2. Set up the environment:

# Install uv if not already installed
pip install uv  # on Linux: pip install uv
brew install uv # On MacOS: brew install uv

# Create a virtual environment and install dependencies
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
uv sync

(You can also directly run setup.sh to set up the environment.)

Usage

Running with npx

You can run the server using npx without needing to install it globally:

# Run using npx (also supports all command-line parameters)
npx -y mcp-trino-python --username user --password pass

Adding to Cursor

Method 1: Using JSON Configuration

You can configure the MCP server by editing Cursor's configuration JSON directly:

1. Open Cursor settings (Cmd+, on Mac or Ctrl+, on Windows/Linux)
2. Click on "Edit in JSON" at the top right
3. Add the following to your configuration:

{
  "mcpServers": {
    "trino-python": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-trino-python",
        "--host",
        "your-trino-host",
        "--port",
        "443",
        "--username",
        "your_username", // Required
        "--password",
        "your_password" // Required
      ]
    }
  }
}

If you've published the package to npm, you can use this configuration:

{
  "mcpServers": {
    "trino-python": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-trino-python",
        "--host",
        "your-trino-host",
        "--port",
        "443",
        "--username",
        "your_username", // Required
        "--password",
        "your_password", // Required
        "--schema",
        "your_schema",
        "--source",
        "tempalte_{username}_adhoc" // Replace it wiht your source identifier
      ]
    }
  }
}

Available Confurations:

Option	Description
--host	Presto/Trino host server (default: localhost)
--port	Server port (default: 8080)
--protocol	Protocol (http/https) (default: https) - Only the selected protocol adapter will be created
--username	Username for authentication (Required)
--password	Password for authentication (Required)
--catalog	Trino catalog name (default: hive)
--schema	Default schema to use for queries (default: default)
--source	Source identifier shown in Trino/Presto UI (default: mcp-trino-python) - Use {username} to include username
--resource-group	Trino resource group or queue name for workload management
--connect-timeout	Connection timeout in seconds (default: 10) - Controls how long to wait when establishing connections
--query-timeout	Query timeout in seconds (default: 300) - Controls both client request timeout and server-side query timeout
--verbose	Show verbose output including credentials

Available MCP Commands

The MCP server supports the following commands:

Command	Description
execute-query	Execute SQL queries with optional limit
list-tables	List all tables in a schema
describe-table	Show table structure including columns
health-check	Check server health and connection status

Example Command Usage

In Cursor IDE, you can use these commands as follows:

1. For executing queries:

   Command: execute-query
   Parameters: {"query": "SELECT * FROM your_table LIMIT 10"}
   

2. For listing tables:

   Command: list-tables
   Parameters: {"schema": "your_schema"}
   

3. For describing a table:

   Command: describe-table
   Parameters: {"table": "your_table", "schema": "your_schema"}
   

Troubleshooting

If you encounter connection issues:

1. Check network connectivity to the Presto/Trino server
2. Run with --verbose flag to see detailed connection information
3. Ensure proper permissions for the specified schema

License

MIT