Skip to main content
Glama
Sign In
Iceberg MCP Server (via Impala)

Iceberg MCP Server (via Impala)

by odog96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Iceberg MCP Server (via Impala)

No user-submitted related servers found.

    Related Servers

    • Cloudera Iceberg MCP Server

      Cloudera Iceberg MCP Serverofficial

      cloudera
      A
      license
      B
      quality
      D
      maintenance
      Enables read-only access to Apache Iceberg tables via Impala, allowing LLMs to inspect database schemas and execute SQL queries to retrieve data from Iceberg tables.
      2
      13
      Apache 2.0

    • akko-mcp-trino

      AKKO-p
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP hosts to query Trino while carrying each end user's verified OIDC identity, so row filters, column masks, and catalog scope are enforced by the existing policy engine rather than a shared service account. Queries are read-only by construction, with quotas, revocation, and audit logging.
      348 PyPI
      7
      Apache 2.0

    • Spark Iceberg MCP Server

      will-sh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only Spark SQL queries against Apache Iceberg tables, allowing LLM clients to inspect schemas and run SELECT-style queries on HDFS/S3 data without Hive or Impala.
      Apache 2.0

    • iceberg-mcp-server-hive

      frothkoetter
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only SQL access to Apache Iceberg tables via HiveServer2, enabling querying, schema discovery, and database listing on Cloudera Data Platform.
      3
      1
      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

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools occupy clearly separate roles: `get_schema` for metadata discovery and `execute_query` for running read-only SQL. There is no realistic scenario where an agent would confuse one for the other, and the descriptions even specify the intended workflow order (schema first, then query).

    Naming Consistency5/5

    Both names follow a strict verb_noun snake_case pattern (`execute_query`, `get_schema`), using consistent verbs and clear object nouns. No mixing of conventions or casing styles.

    Tool Count4/5

    Two tools is on the thin side relative to the typical 3-15 range, but for a deliberately read-only SQL access layer both tools earn their place and form a complete minimal workflow. It is slightly under-provisioned but not wasteful or confusing.

    Completeness4/5

    The surface covers the core read-only lifecycle: inspect schema, then query. Minor conveniences (e.g. dedicated list-databases, table description, or EXPLAIN helper) are absent, but an agent can reach equivalent results by issuing SHOW/DESCRIBE through `execute_query`, so no hard dead ends exist. Write operations are intentionally excluded.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources