Skip to main content
Glama
manojjain10

Cloudera Hive MCP Server

by manojjain10

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HIVE_HOSTYesVirtual Warehouse hostname
HIVE_PORTNoHTTPS port443
HIVE_PASSWORDYesCloudera workload password
HIVE_USERNAMEYesCloudera workload user
HIVE_HTTP_PATHNoHiveServer2 HTTP path/cliservice
HIVE_READ_ONLYNoIf true, execute_query rejects DDL/DMLtrue
HIVE_QUERY_ROW_LIMITNoMax rows returned by execute_query1000

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_databasesA

Retrieve all available databases in the Hive Virtual Warehouse.

list_tablesB

Retrieve all tables for a given database.

describe_tableA

Return column names, types, and comments for database.table.

get_table_sampleA

Preview the first limit rows of database.table (1..100).

execute_queryA

Execute a HiveQL query and return results as a list of row dicts.

When HIVE_READ_ONLY is true (the default), write DDL/DML is rejected. Results are capped at HIVE_QUERY_ROW_LIMIT rows.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a distinct responsibility: describing table schema, executing queries, sampling data, listing databases, and listing tables. No two tools overlap in purpose, ensuring clear selection.

Naming Consistency5/5

All tools use a consistent verb_noun pattern in snake_case (e.g., describe_table, execute_query). This makes the toolset predictable and easy to navigate.

Tool Count5/5

With 5 tools, the server covers core Hive operations without being bloated or sparse. Each tool serves a necessary function for a read-only Hive interface.

Completeness4/5

The tools provide fundamental read-only capabilities: schema discovery, data preview, and query execution. A minor gap is the lack of tools for obtaining table statistics or partition info, but the set is largely complete for its purpose.

Maintenance

ActivityStale
ResponsivenessNo issues