Skip to main content
Glama
ahodroj

MCP Iceberg Catalog

by ahodroj

Catálogo Iceberg MCP

insignia de herrería

Implementación de un servidor MCP (Protocolo de Contexto de Modelo) para interactuar con Apache Iceberg. Este servidor proporciona una interfaz SQL para consultar y gestionar tablas de Iceberg a través del escritorio Claude.

Claude Desktop como su catálogo de Iceberg Data Lake

imagen

Related MCP server: Databricks MCP Server

Cómo instalar en Claude Desktop

Instalación mediante herrería

Para instalar MCP Iceberg Catalog para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install @ahodroj/mcp-iceberg-service --client claude
  1. Prerrequisitos

    • Python 3.10 o superior

    • Instalador de paquetes UV (recomendado) o pip

    • Acceso a un catálogo REST de Iceberg y almacenamiento compatible con S3

  2. Cómo instalar en Claude Desktop Agregue la siguiente configuración a claude_desktop_config.json :

{
  "mcpServers": {
    "iceberg": {
      "command": "uv",
      "args": [
        "--directory",
        "PATH_TO_/mcp-iceberg-service",
        "run",
        "mcp-server-iceberg"
      ],
      "env": {
        "ICEBERG_CATALOG_URI" : "http://localhost:8181",
        "ICEBERG_WAREHOUSE" : "YOUR ICEBERG WAREHOUSE NAME",
        "S3_ENDPOINT" : "OPTIONAL IF USING S3",
        "AWS_ACCESS_KEY_ID" : "YOUR S3 ACCESS KEY",
        "AWS_SECRET_ACCESS_KEY" : "YOUR S3 SECRET KEY"
      }
    }
  }
}

Diseño

Arquitectura

El servidor MCP se basa en tres componentes principales:

  1. Manejador de protocolo MCP

    • Implementa el Protocolo de Contexto Modelo para la comunicación con Claude

    • Maneja ciclos de solicitud/respuesta a través de stdio

    • Gestiona el ciclo de vida y la inicialización del servidor.

  2. Procesador de consultas

    • Analiza consultas SQL usando sqlparse

    • Apoya operaciones:

      • LISTA DE TABLAS

      • DESCRIBIR TABLA

      • SELECCIONAR

      • INSERTAR

  3. Integración de Iceberg

    • Utiliza pyiceberg para operaciones de tabla

    • Se integra con PyArrow para un manejo eficiente de datos.

    • Administra las conexiones del catálogo y las operaciones de tabla.

Integración de PyIceberg

El servidor utiliza PyIceberg de varias maneras:

  1. Gestión de catálogos

    • Se conecta a catálogos REST

    • Administra los metadatos de la tabla

    • Maneja operaciones de espacio de nombres

  2. Operaciones de datos

    • Convierte entre tipos PyIceberg y PyArrow

    • Maneja la inserción de datos a través de tablas de PyArrow

    • Administra esquemas de tablas y tipos de campos

  3. Ejecución de consultas

    • Traduce SQL a operaciones de PyIceberg

    • Maneja el escaneo y filtrado de datos

    • Gestiona la conversión del conjunto de resultados

Se necesita mayor implementación

  1. Operaciones de consulta

    • [ ] Implementar operaciones UPDATE

    • [ ] Agregar soporte para ELIMINAR

    • [ ] Soporte para CREATE TABLE con definición de esquema

    • [ ] Agregar operaciones ALTER TABLE

    • [ ] Implementar soporte para particionamiento de tablas

  2. Tipos de datos

    • [ ] Soporte para tipos complejos (matrices, mapas, estructuras)

    • [ ] Agregar marca de tiempo con manejo de zona horaria

    • [ ] Soporte para tipos decimales

    • [ ] Agregar soporte para campos anidados

  3. Mejoras de rendimiento

    • [ ] Implementar inserciones por lotes

    • [ ] Agregar optimización de consultas

    • [ ] Soporte para escaneos paralelos

    • [ ] Agregar capa de almacenamiento en caché para datos a los que se accede con frecuencia

  4. Características de seguridad

    • [ ] Agregar mecanismos de autenticación

    • [ ] Implementar control de acceso basado en roles

    • [ ] Agregar seguridad a nivel de fila

    • [ ] Soporte para conexiones cifradas

  5. Monitoreo y gestión

    • [ ] Agregar colección de métricas

    • [ ] Implementar el registro de consultas

    • [ ] Agregar supervisión del rendimiento

    • [ ] Soporte para operaciones de mantenimiento de tablas

  6. Manejo de errores

    • [ ] Mejorar los mensajes de error

    • [ ] Agregar mecanismos de reintento para fallas transitorias

    • [ ] Implementar soporte para transacciones

    • [ ] Agregar validación de datos

Available Tools

1 tool
execute_queryC

Execute a query on Iceberg tables

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesQuery to execute (supports: LIST TABLES, DESCRIBE TABLE, SELECT, CREATE TABLE)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It mentions the query types supported (LIST TABLES, DESCRIBE TABLE, SELECT, CREATE TABLE), which adds some context, but fails to address critical aspects like permissions needed, whether it's read-only or mutating, error handling, or output format expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a query execution tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error handling, permissions, or what to expect from results, leaving significant gaps for an AI agent to operate effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, explicitly documenting the 'query' parameter with supported query types. The description does not add any additional semantic details beyond what the schema already provides, so it meets the baseline for adequate but unremarkable coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Execute a query') and target resource ('on Iceberg tables'), providing a specific verb+resource combination. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, so it falls short of a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It merely states what the tool does without indicating appropriate scenarios or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedexecute_query

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name follows a clear verb_noun pattern (execute_query).

Tool Count2/5

A single tool is too few for a catalog server, which typically requires operations like list_tables, get_table, create_table, or update_metadata to be useful. This minimal set severely limits functionality and scope.

Completeness1/5

The tool set is severely incomplete for an Iceberg catalog domain, lacking basic CRUD operations such as listing, creating, or managing tables. With only a query execution tool, agents cannot perform essential catalog tasks, leading to dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables Claude to execute SQL queries on Snowflake databases with automatic connection lifecycle management.
    45
    MIT
  • A
    license
    C
    quality
    D
    maintenance
    An MCP server that enables natural language interaction with Apache Iceberg data lakehouses, allowing users to query table metadata, schemas, and properties through Claude, Cursor, or other MCP clients.
    5
    41
    Apache 2.0
  • A
    license
    B
    quality
    C
    maintenance
    A Model Context Protocol server that provides seamless integration with Trino and Iceberg, enabling data exploration, querying, and table maintenance through a standard interface.
    22
    25
    Apache 2.0

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ahodroj/mcp-iceberg-service'

If you have feedback or need assistance with the MCP directory API, please join our Discord server