Install and load the iceberg extension: INSTALL iceberg; LOAD iceberg
Create a secret for catalog authentication if required, e.g.: CREATE SECRET my_catalog_secret (TYPE ICEBERG, TOKEN 'bearer-token-value')
Attach the catalog: ATTACH 'https://catalog-host/api/catalog' AS my_catalog (TYPE ICEBERG, WAREHOUSE 'warehouse_name')
List available tables: SHOW ALL TABLES or USE my_catalog; SHOW TABLES
Query a table directly using three-part naming: SELECT * FROM my_catalog.my_namespace.my_table
Known gotchas
The ATTACH statement for Iceberg REST catalogs requires the iceberg extension to be loaded first; calling ATTACH before LOAD iceberg raises an unrecognized type error
Credential vending (where the catalog returns temporary cloud credentials) must be supported by the catalog server; if it is not, you must separately configure httpfs secrets for the underlying storage
The WAREHOUSE parameter in ATTACH must match a warehouse identifier known to the catalog server; mismatches result in a 404 or empty namespace list
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp