Cloudera Iceberg MCP Server

Official

by cloudera

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Related Servers

Alternatives to Cloudera Iceberg MCP Server

No user-submitted related servers found.

Related Servers

Cloudera Iceberg MCP Server
Databases Data Platforms Search
peterableda
A
license
Not graded
quality
C
maintenance
Provides read-only access to Iceberg tables via Apache Impala, enabling LLMs to inspect database schemas and execute SQL queries on Iceberg data.
Updated a year ago (2025-06-27 22:18 UTC)
Apache 2.0
Spark Iceberg MCP Server
Databases Data Platforms
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.
Updated a month ago (2026-09-17 03:02 UTC)
Apache 2.0
iceberg-mcp-server-hive
Databases Data Platforms
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.
Updated a month ago (2026-09-14 11:49 UTC)
3
Apache 2.0
impala-mcp-server
Databases Data Platforms
yaowenqiang
A
license
A
quality
C
maintenance
Enables AI agents to safely query and explore Apache Impala clusters with read-only SQL, metadata, statistics, cluster overview, and analysis prompt templates.
Updated a month ago (2026-09-16 09:50 UTC)
17
Apache 2.0
IcebergMCP
Databases Data Platforms
fastmcp-me
A
license
C
quality
D
maintenance
Enables natural language interaction with Apache Iceberg Lakehouse tables through MCP, supporting read-only operations like listing namespaces, tables, schemas, and partitions.
Updated 9 months ago (2026-01-04 23:03 UTC)
5
Apache 2.0
Iceberg MCP Server
Databases Search
inirah02
A
license
Not graded
quality
D
maintenance
Enables natural language querying of Apache Iceberg lakehouse by exposing typed tools for namespace discovery, table metadata inspection, snapshot history, time travel SQL generation, and partition pruning explanation.
Updated 4 months ago (2026-06-26 17:36 UTC)
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

B3.3/5.0

Scored 2026-04-18 07:36 across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: execute_query runs SQL queries and returns results, while get_schema retrieves metadata about table names. There is no overlap in functionality or ambiguity about when to use each tool.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (execute_query, get_schema) with clear action-object relationships. The naming style is uniform throughout the set.

Tool Count2/5

With only 2 tools for a database/query server, the surface feels severely limited. While the tools cover basic query execution and schema inspection, typical database operations like table creation, data manipulation, or metadata exploration beyond table names are missing, making this feel under-scoped.

Completeness2/5

For an Impala/Cloudera Iceberg database server, the toolset is significantly incomplete. There are no tools for creating/dropping tables, inserting/updating data, managing partitions, or accessing detailed schema information beyond table names. This creates dead ends for agents trying to perform common database operations.