Runs can be launched and terminated but not updated. Assets can be materialised but not deleted. Logs are read-only. Those absences are the design: the destructive operations that would matter in a data platform are simply not there, while alert policies and issues — the low-stakes bookkeeping — get full CRUD. Publishing a matrix instead of tool names is less convenient for us and clearer about the boundary. Being a Labs preview, expect movement.
Dagster's endpoint for Dagster+. Their documentation publishes a capability matrix rather than tool names: which objects can be viewed, created, updated, deleted, and which expose Insights metrics.
- Runs — view, launch, terminate, and Insights metrics; there is no update
- Run logs — view only
- Assets — view, materialise, and Insights metrics; no update or delete
- Deployments — view, with Insights metrics
- Alert policies and Dagster+ Issues — full create, update and delete
OAuth in the browser, or a bearer user token with a Dagster-Cloud-Organization header, scope dagster.mcp. This is a Labs preview and the APIs may change; it is not available for Dagster OSS.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen