This is a A Model Context Protocol server that provides read-only access to Iceberg tables via Apache Impala. This server enables LLMs to inspect
Iceberg original mcp server connects Iceberg Original to AI assistants that speak the Model Context Protocol. This is a A Model Context Protocol server that provides read-only access to Iceberg tables via Apache Impala. This server enables LLMs to inspect database schemas and execute read-only queries.
This is a A Model Context Protocol server that provides read-only access to Iceberg tables via Apache Impala. This server enables LLMs to inspect database schemas and execute read-only queries.
Once connected, the assistant can call this tool directly:
Transport — The MCP server's transport protocol is configurable via the MCP_TRANSPORT environment variable. Supported values: - stdio (default) — communicate overSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
The server reads 5 environment variables: IMPALA_HOST, IMPALA_PORT, IMPALA_USER, IMPALA_PASSWORD, IMPALA_DATABASE. Keep credentials in your client's env block or a secrets manager rather than committing them.
Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. Iceberg Original sits in that group, and the shape of its toolset — Transport — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Transport | The MCP server's transport protocol is configurable via the MCP_TRANSPORT environment variable. Supported values: - stdio **(default)** — communicate over standard input/output. Useful for local tools, command-line scrip |
{
"mcpServers": {
"iceberg-mcp-server": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/cloudera/iceberg-mcp-server@main",
"run-server"
],
"env": {
"IMPALA_HOST": "coordinator-default-impala.example.com",
"IMPALA_PORT": "443",
"IMPALA_USER": "username",
"IMPALA_PASSWORD": "password",
"IMPALA_DATABASE": "default"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| IMPALA_HOST | Endpoint or connection string the server talks to. | Optional |
| IMPALA_PORT | Configuration value read at startup. | Optional |
| IMPALA_USER | Configuration value read at startup. | Optional |
| IMPALA_PASSWORD | Configuration value read at startup. | Optional |
| IMPALA_DATABASE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.