Start the Unity Catalog OSS server and note the base URL (default: http://localhost:8080)
List catalogs with GET /api/2.1/unity-catalog/catalogs to confirm the server is running
Create a table by sending POST /api/2.1/unity-catalog/tables with a JSON body specifying catalog_name, schema_name, name, table_type (MANAGED or EXTERNAL), data_source_format, and columns
Retrieve table metadata with GET /api/2.1/unity-catalog/tables/{full_name} where full_name is catalog.schema.table
Delete a table with DELETE /api/2.1/unity-catalog/tables/{full_name}
Known gotchas
Unity Catalog OSS uses the /api/2.1/unity-catalog/ prefix, which differs from Databricks-hosted Unity Catalog REST paths; do not conflate the two
For EXTERNAL tables you must supply a storage_location; for MANAGED tables the server controls the path, and providing one is ignored or may cause an error
The OSS server ships without authentication by default; in production, enable auth via configuration before exposing the API endpoint
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