MCP Iceberg Catalog

Created By
ahodroja year ago
MCP server for interacting with Apache Iceberg catalog from Claude, enabling data lake discovery and metadata search through a LLM prompt.
Overview

What is MCP Iceberg Catalog?

MCP Iceberg Catalog is a server implementation for interacting with Apache Iceberg, enabling data lake discovery and metadata search through a LLM prompt.

How to use MCP Iceberg Catalog?

To use the MCP Iceberg Catalog, install it via Smithery in Claude Desktop by running a specific command in your terminal and configuring the necessary settings in the claude_desktop_config.json file.

Key features of MCP Iceberg Catalog?

  • SQL interface for querying and managing Iceberg tables.
  • Integration with Claude desktop for enhanced data lake management.
  • Support for various SQL operations like LIST TABLES, DESCRIBE TABLE, SELECT, and INSERT.

Use cases of MCP Iceberg Catalog?

  1. Managing and querying large datasets in data lakes.
  2. Facilitating metadata search for Iceberg tables.
  3. Enabling data operations through a user-friendly SQL interface.

FAQ from MCP Iceberg Catalog?

  • What are the prerequisites for installation?

You need Python 3.10 or higher, a UV package installer, and access to an Iceberg REST catalog and S3-compatible storage.

  • Can I use it without Claude Desktop?

The MCP Iceberg Catalog is designed to work with Claude Desktop for optimal performance and usability.

  • What SQL operations are supported?

Currently, it supports LIST TABLES, DESCRIBE TABLE, SELECT, and INSERT operations, with more features planned for future updates.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ahodroj
Star
2
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago