Skip to main content
Glama
apache

drill-mcp

Official
by apache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to drill-mcp

No user-submitted related servers found.

    Related Servers

    • telemetry-mcp

      selamy-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.
      MIT

    • dremio-mcp-lite

      guillaume-galp
      A
      license
      A
      quality
      C
      maintenance
      A lightweight MCP server for exploring Dremio data catalogs. It provides read-only tools for browsing catalogs, querying tables, and previewing data.
      6
      1 npm
      MIT

    • sql-explorer-mcp

      govern-agents
      A
      license
      Not graded
      quality
      F
      maintenance
      Read-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.
      MIT

    • mcp-mssqlserver

      ferronicardoso
      A
      license
      A
      quality
      C
      maintenance
      Production-oriented MCP server for Microsoft SQL Server, enabling query execution, database discovery, schema introspection, and metadata inspection via MCP clients.
      6
      4
      MIT

    • duckcoop

      minsc-of-secrets
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for sandboxed, read-only SQL queries on CSV/Parquet/JSON files via DuckDB, limited to a specified directory.
      1
      MIT

    • dbeaver-mcp-server

      dongchao-1
      F
      license
      A
      quality
      C
      maintenance
      MCP server that reads DBeaver database configurations and provides SQL execution via existing JDBC drivers — no extra driver downloads needed.
      3
      -
    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.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: query execution, schema/table listing, table description, storage plugin configs, cluster status, and query profile management. There is no overlap in purpose, so an agent can reliably select the correct tool.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern using snake_case (run_query, list_schemas, list_tables, describe_table, list_storage_plugins, list_profiles, get_profile, cancel_query). The only deviation is 'cluster_status', which lacks an explicit verb but remains clear and readable.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a Drill MCP server. It covers metadata exploration, query execution, cluster health, and query management without unnecessary bloat, fitting comfortably within the ideal 3-15 range.

    Completeness4/5

    The server covers the core lifecycle of query interaction: running a query, inspecting profiles, and canceling. It also provides comprehensive metadata browsing via schemas, tables, and columns. Minor gaps exist such as lack of write operations or cross-schema table listing, but these are not critical for typical read-oriented Drill usage.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources