Skip to main content
Glama
lakehouse-42

@lakehouse/mcp-server

by lakehouse-42

Related Servers

Alternatives to @lakehouse/mcp-server

No user-submitted related servers found.

    Related Servers

    • 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
      Not graded
      quality
      C
      maintenance
      MCP server providing seamless integration with Trino and Iceberg for advanced data exploration, querying, and table maintenance.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP Server for Apache Iceberg, enabling users to read, query, and manipulate data within Iceberg catalogs.
      222 PyPI
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants the ability to connect to, query, profile, and monitor data sources — turning any LLM into an interactive data engineering copilot.
      MIT

    TDQS

    B3.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools are largely distinct: search_tools is meta, search and ask_question target different retrieval modes, and time_travel tools are clearly separated. Some confusion could arise between search and ask_question since both retrieve information, but descriptions clarify the intent.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_document, list_documents, upload_document). A few deviate like 'search' (bare verb) and 'time_travel_diff' (noun-heavy), but overall naming is predictable and readable.

    Tool Count5/5

    With 10 tools, the server is well-scoped. Each tool serves a distinct function within the two core domains (document search/RAG and time-travel on Iceberg), and none feel redundant or unnecessary.

    Completeness3/5

    The document side covers upload, retrieval, and search but lacks update and delete operations, which are common CRUD gaps. The time-travel features are useful but assume knowledge of tables/snapshots without a listing mechanism; overall the surface is functional but not fully comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues