iceberg-mcp-server-hive
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HIVE_HOST | Yes | HiveServer2 or Knox gateway host | |
| HIVE_PORT | No | HS2 port (443 for Knox HTTP) | 443 |
| HIVE_USER | Yes | LDAP / service user | |
| HIVE_USE_SSL | No | TLS | true |
| HIVE_DATABASE | No | Default database for SHOW TABLES | default |
| HIVE_PASSWORD | Yes | Password | |
| MCP_TRANSPORT | No | stdio, http, or sse | stdio |
| HIVE_HTTP_PATH | No | Knox / HS2 HTTP path | cliservice |
| HIVE_AUTH_MECHANISM | No | impyla auth mechanism | LDAP |
| HIVE_USE_HTTP_TRANSPORT | No | HTTP transport (typical on CDP) | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryA | Execute a read-only SQL query on Hive (Iceberg tables) and return JSON results. |
| get_schemaA | List table names in the configured Hive database, or in an optional database. |
| list_databasesA | List all Hive databases visible to the connected user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct function: executing queries, listing tables, and listing databases. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern using snake_case, making them predictable and easy to understand.
With only three tools, the server is minimal but covers the essential read-only operations for Hive databases. The count is reasonable given the focused scope.
The server lacks a tool for retrieving detailed table schema or previewing data, which are common needs when exploring databases. This is a notable gap for a read-only explorer.