Skip to main content
Glama
weijie-tan3

Trino MCP Server

by weijie-tan3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Trino MCP Server

No user-submitted related servers found.

    Related Servers

    • @arkty/redash-mcp

      arkty
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables executing SQL queries, exploring database schemas, and exporting results from Redash via MCP, with ad-hoc queries and write protection.
      5 npm
      MIT

    • mcp-sql-multi

      rajivdatta
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying multiple SQL Server, Azure SQL, or Synapse databases through a single MCP interface, with support for read-only targets and various authentication methods.
      MIT

    • MCP Trino Server

      fastmcp-me
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing seamless integration with Trino and Iceberg for advanced data exploration, querying, and table maintenance.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: listing catalogs/schemas/tables, getting table metadata, and executing queries. The two query execution tools are differentiated by read-only vs. write-capable, and describe_table vs. show_create_table both deal with table structure but with different outputs. Minor overlap exists but descriptions resolve ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_*, describe_table, execute_query, show_create_table, get_table_stats), using lowercase snake_case throughout. The read-only query tool is named as a clear modifier of execute_query, maintaining consistency.

    Tool Count5/5

    The 8 tools are well-scoped for a Trino query server, covering metadata exploration and query execution without redundancy. The count is within the ideal 3-15 range and each tool serves a specific need.

    Completeness4/5

    The tool surface covers the primary use cases: discovering catalogs/schemas/tables, inspecting table structure, retrieving table statistics, and running read-only or write queries. Minor gaps exist, such as lack of explicit query cancellation or history, but these are not critical for typical Trino interactions and can be handled via SQL.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources