Cloudera Iceberg MCP Server via Impala
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-genai-works-org-cloudera-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Iceberg MCP Server - Setup Guide Complete setup instructions for the Iceberg MCP Server with HTTP transport support. ## Prerequisites - **Python 3.10+** - **Access to Cloudera Data Platform** with Impala - **Valid Cloudera credentials** - **uv** package manager (recommended) or pip ### Install UV (if not already installed) ```bash # macOS/Linux curl -LsSf https://astral.sh/uv/install.sh | sh # Windows powershell -c "irm https://astral.sh/uv/install.ps1 | iex" # Or via pip pip install uv ``` ## Installation ### Step 1: Clone the Repository ```bash git clone https://github.com/genai-works-org/cloudera-mcp cd cloudera-mcp ``` ### Step 2: Install Dependencies ```bash # Sync existing project dependencies uv sync # Install project in editable mode uv pip install -e . ``` ## Configuration ### Step 3: Create Environment Configuration Create a `.env` file in the project root directory: ```bash # Create .env file with your Cloudera credentials cat > .env << EOF # Cloudera Impala Configuration IMPALA_HOST=your-coordinator-host.cloudera.site IMPALA_PORT=443 IMPALA_USER=your-username IMPALA_PASSWORD=your-password IMPALA_DATABASE=default IMPALA_AUTH_MECHANISM=LDAP IMPALA_USE_HTTP_TRANSPORT=true IMPALA_HTTP_PATH=cliservice IMPALA_USE_SSL=true EOF ``` ### Step 4: Update Configuration Values Edit the `.env` file with your actual credentials: **For Cloudera Data Platform:** - **IMPALA_HOST**: Your Cloudera coordinator hostname - **IMPALA_USER**: Your Cloudera username - **IMPALA_PASSWORD**: Your Cloudera password - **IMPALA_AUTH_MECHANISM**: Usually `LDAP` for CDP **Example from JDBC connection string:** ``` jdbc:impala://coordinator-xyz123.dw-xyz123.cloudera.site:443/default;AuthMech=3;transportMode=http;httpPath=cliservice;ssl=1;UID=myuser;PWD=mypass ``` Converts to: ```bash IMPALA_HOST=coordinator-xyz123.dw-xyz123.cloudera.site IMPALA_PORT=443 IMPALA_USER=myuser IMPALA_PASSWORD=mypass IMPALA_AUTH_MECHANISM=LDAP ``` ## Verification ### Step 6: Test Databas…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.