Apache Hive MCP Server
Enables LLM agents to query Apache Hive/HiveServer2 by listing tables and running read-only SQL, with results returned as JSON.
README
Apache Hive MCP Server
An MCP server for Apache Hive (HiveServer2), built with FastMCP. Connects to any HiveServer2-compatible endpoint — open-source Apache Hive, Cloudera CDP Base, or Cloudera CDP Public Cloud (CDW) — and exposes two read-only tools that an LLM agent can call.
Project summary
- What it is — a Model Context Protocol server that lets an LLM agent query Apache Hive: list tables and run read-only SQL, with results returned as JSON.
- Feature parity — mirrors Cloudera's
Impala/Iceberg MCP server:
same
execute_query+get_schematools and structure, with the connection layer swapped to HiveServer2 viaimpyla. - Works everywhere HiveServer2 does — open-source Apache Hive, CDP Base
(Kerberos/LDAP), and CDP Public Cloud / CDW (Knox, LDAP over HTTPS). Auth,
transport, and TLS are all driven by
HIVE_*environment variables. - Safe by default —
execute_queryenforces a read-only prefix guard (SELECT/SHOW/DESCRIBE/WITH); write/DDL statements are rejected before a connection is opened. - Transport —
stdio(default),http, orsse, selected viaMCP_TRANSPORT. - Tech stack — Python ≥3.10, FastMCP,
impyla,uv. 11 unit tests (connection mocked — no live Hive required).
Tools
| Tool | Signature | Description |
|---|---|---|
execute_query |
execute_query(query: str) -> str |
Execute a read-only SQL query (SELECT, SHOW, DESCRIBE, WITH) and return results as a JSON array of column-keyed objects. Write operations are rejected with an error string. |
get_schema |
get_schema() -> str |
Run SHOW TABLES against the configured database and return the table list as a JSON array of strings. |
Configuration
All configuration is via environment variables (or a .env file at the project root).
| Variable | Default | Description |
|---|---|---|
HIVE_HOST |
localhost |
HiveServer2 hostname or IP |
HIVE_PORT |
10000 |
HiveServer2 thrift port |
HIVE_DATABASE |
default |
Database to connect to |
HIVE_USER |
(empty) | Username (leave empty for NOSASL/Kerberos) |
HIVE_PASSWORD |
(empty) | Password (used with PLAIN/LDAP) |
HIVE_AUTH_MECHANISM |
PLAIN |
Auth method: NOSASL, PLAIN, LDAP, GSSAPI |
HIVE_USE_HTTP_TRANSPORT |
false |
Use HTTP transport instead of binary thrift |
HIVE_HTTP_PATH |
cliservice |
HTTP path when HIVE_USE_HTTP_TRANSPORT=true |
HIVE_USE_SSL |
false |
Enable TLS for the thrift connection |
HIVE_KERBEROS_SERVICE_NAME |
hive |
Kerberos service principal name (GSSAPI only) |
MCP_TRANSPORT |
stdio |
MCP transport: stdio, http, or sse |
Copy .env.example to .env and fill in your values.
Deployment presets
Local / development (Docker HiveServer2)
HIVE_HOST=localhost
HIVE_PORT=10000
HIVE_DATABASE=default
HIVE_AUTH_MECHANISM=NOSASL
MCP_TRANSPORT=stdio
CDP Public Cloud (CDW Virtual Warehouse)
HIVE_HOST=<coordinator-hostname>.dw.cloudera.site
HIVE_PORT=443
HIVE_DATABASE=default
HIVE_USER=<workload-username>
HIVE_PASSWORD=<workload-password>
HIVE_AUTH_MECHANISM=LDAP
HIVE_USE_HTTP_TRANSPORT=true
HIVE_HTTP_PATH=cliservice
HIVE_USE_SSL=true
MCP_TRANSPORT=stdio
CDP Base / on-premises with Kerberos
HIVE_HOST=<hiveserver2-host.example.com>
HIVE_PORT=10000
HIVE_DATABASE=default
HIVE_AUTH_MECHANISM=GSSAPI
HIVE_KERBEROS_SERVICE_NAME=hive
MCP_TRANSPORT=stdio
Obtain a Kerberos ticket (
kinit) before starting the server.
Running
# Install
pip install -e .
# or with uv:
uv sync
# Copy and edit config
cp .env.example .env
# Start (stdio transport, for use with an MCP host)
uv run hive-mcp-server
MCP client configuration
MCP hosts (Claude Desktop, Cloudera AI Agent Studio, etc.) register servers with
a mcpServers JSON block. uvx runs this server straight from GitHub — no
local install or PyPI publish required. Fill in the HIVE_* values for your
environment (see Configuration and the presets above).
{
"mcpServers": {
"Hive": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/avelloal/hive-mcp-server@v0.1.0",
"hive-mcp-server"
],
"env": {
"HIVE_HOST": "<coordinator-hostname>.dw.cloudera.site",
"HIVE_PORT": "443",
"HIVE_DATABASE": "default",
"HIVE_USER": "<workload-username>",
"HIVE_PASSWORD": "<workload-password>",
"HIVE_AUTH_MECHANISM": "LDAP",
"HIVE_USE_HTTP_TRANSPORT": "true",
"HIVE_HTTP_PATH": "cliservice",
"HIVE_USE_SSL": "true"
}
}
}
}
The example above targets CDP Public Cloud / CDW. For local or Kerberos
targets, swap the env values using the presets above.
@v0.1.0 pins a fixed release — drop it to track the latest, or bump it for a
newer version.
For Cloudera AI Agent Studio specifically (registration steps, env-var
handling, stdio/uvx limitations), see
examples/agent-studio/.
Smoke test
- Start a local HiveServer2 (e.g., Apache Hive Docker image):
docker run -d -p 10000:10000 apache/hive:3.1.3 - Configure
.envwith the local preset above. - Start the server:
uv run hive-mcp-server - In a second terminal, use the
fastmcpdev inspector or any MCP client to call both tools:get_schema()— should return[]or a list of table names.execute_query("SHOW DATABASES")— should return a JSON array of databases.
License
Apache License 2.0 — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.