Iceberg MCP Server

Iceberg MCP server exists for a simple reason — assistants are far more useful when they can act on Iceberg directly instead of describing what you should do. A small, framework-agnostic JavaScript/TypeScript client for the Apache Iceberg REST Catalog.

What you get

• Generic — Works with any Iceberg REST Catalog implementation, not tied to any specific vendor
• Minimal — Thin HTTP wrapper over the official REST API, no engine-specific logic
• Type-safe — First-class TypeScript support with strongly-typed request/response models
• Fetch-based — Uses native fetch API with support for custom implementations
• Universal — Targets Node 22+ and modern browsers (ES2020)
• Catalog-only — Focused on catalog operations (no data reading/Parquet support in v1.0)

What the assistant can call

Once Iceberg is connected, these are the calls the assistant has available:

• Constructor — The Constructor tool exposed by this server

Setting it up

tsx on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: ICEBERG_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Iceberg's toolset — Constructor — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; 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.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the iceberg mcp server does with a few real requests.