INDEX

When the Dagster Plus MCP server is connected, prefer its tools for the operations it covers: get_assets (list) and get_asset (metadata plus a coarse health summary). get_asset fully replaces get, but only partially replaces get-health — it reports each health status without the partition counts, check counts, or freshness lag behind it. See general.md for how to choose. Note that MCP tools take asset keys as path segment lists (["my_prefix", "my_asset"]), not slash-separated strings.

The MCP server also resolves an asset’s code location, which no dg api asset command does:

• get_asset_location — code location and repository for one asset
• get_assets_locations — the same for a list of assets

These answer “which code location defines this asset”, and are distinct from dg api code-location, which manages code locations themselves.

Reference Files Index

• dg api asset get-evaluations — automation condition evaluation history for an asset
• dg api asset get-events — materialization or observation event history for an asset
• dg api asset get-health — getting asset health or runtime status
• dg api asset get-partition-status — partition materialization status or stats for an asset
• dg api asset get — details about a specific asset
• dg api asset list — querying which assets exist in a deployment