IcebergMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICEBERG_MCP_REGION | No | The AWS region to use. This is used to determine the catalog and object storage location. us-east-1 by default. | us-east-1 |
| ICEBERG_MCP_PROFILE | No | The AWS profile name to use. This role will be assumed and used to connect to the catalog and the object storage. If not specified, the default role will be used. | default |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_namespacesB | Provides a list of namespaces from the Iceberg catalog. |
| get_iceberg_tablesA | Provides a list of iceberg tables from the Iceberg catalog for a given namespace |
| get_table_schemaC | Provides the schema for a given Iceberg table |
| get_table_propertiesD | – |
| get_table_partitionsC | Provides the partitions for a given Iceberg table |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of the Iceberg catalog (tables list, namespaces, partitions, properties, schema). However, get_table_properties has no description, causing potential confusion with get_table_schema or other tools.
All tool names follow a consistent 'get_noun' pattern with snake_case, making the API predictable and easy to navigate.
Five tools is a reasonable number for a focused read-only catalog client. Each tool serves a clear purpose without redundancy.
The tool set is limited to read operations (list, get) and lacks write operations (create, drop, update) commonly needed for full lifecycle management of Iceberg tables and namespaces.