DE//AGENT
Explore

Learn

metadata

6 registry resources · 3 tutorials, 1 mcp server · roadmap: Observability, Lakehouse

What this topic covers

DE//AGENT currently lists 6 resources under metadata: 3 tutorials, 1 mcp server, 1 agent. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Also present: 1 reference.

What you can learn here

Documented learning objectives across these resources:

1 more objectives live on the individual resource pages.

Where this fits in the learning roadmap

These resources map to stages: Observability (4), Lakehouse (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Compare the registry's options

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

ResourceTypeDifficultyVerificationScore
DataHub MCP ServerMCP serverintermediatecommunity flags42.2
Your first lakehouse table — create, query, measure, compactTutorialbeginnercommunity34.15
Table format mechanics — snapshots, manifests, and the metadata tablesTutorialintermediatecommunity34.15
Catalogs and ownership: who owns this table and is it safe to use?Tutorialbeginnercommunity flags31.15
Data Catalog AssistantAgentbeginnercommunity flags30.5
DataHub DocumentationReference—community26.7

How scores are computed: source quality score.

Where to start

Highest composite score first:

  1. DataHub MCP Server score 42.2 — intermediate
  2. Your first lakehouse table — create, query, measure, compact score 34.15 — beginner
  3. Table format mechanics — snapshots, manifests, and the metadata tables score 34.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Good fits

Cautions and limitations

Security-flagged entries: DataHub MCP Server (2 flags), Catalogs and ownership: who owns this table and is it safe to use? (2 flags), Data Catalog Assistant (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

Production use cases

  • DataHub MCP Server — Exposes a DataHub catalog: search entities, read lineage and schema, and inspect metadata, so an agent can answer "what is this table and what depends on it?". details
  • Your first lakehouse table — create, query, measure, compact — Run the whole loop in one sitting on a scratch table: create and query a first Delta or Iceberg table from the official docs, read its health from the files metadata table with one… details
  • Table format mechanics — snapshots, manifests, and the metadata tables — Open the hood on an Iceberg table: the spec's layers (snapshots, manifests, hidden partitioning), the files and history metadata tables you query with plain SQL, and the manifest l… details
  • Catalogs and ownership: who owns this table and is it safe to use? — Every incident resolves faster when you can ask a catalog what this data is, who owns it, and whether it is safe to use. Run the catalog-assistant workflow end to end — resolve, re… details

Install and inspect

Real install commands from the registry — read the source before running any of them:

uvx mcp-server-datahub

DataHub MCP Server — review first

Further study

Adjacent topics: catalog (4 shared), tutorial (3 shared), lineage (3 shared), lakehouse (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.

Full resource list

← All topics