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
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. The iceberg mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
Transport — The MCP server's transport protocol is configurable via the MCP_TRANSPORT environment variable. Supported values: - stdio (default) — communicateYou will need 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 in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Iceberg's toolset — Transport — is a fair guide to whether it matches your workflow. It is maintained by cloudera; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| 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.