Dbt Docs
Search a dbt project's graph and trace lineage — including column-level lineage — from manifest.json and catalog.json.Read full description
mattijsdpLABSCO SUMMARY
The capability matrix is unusually honest about what an agent cannot do, which is the useful half.
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. A matrix instead of tool names says less about exactly what an agent will call, and more clearly where its reach ends. It is still a beta feature, so expect movement.
What it is
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.
What you get
- 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
Requirements
Sign in to Dagster+ over OAuth in the browser, or send a Dagster+ user token as a Bearer header together with a Dagster-Cloud-Organization header. Organizations in the EU region use https://mcp.agent.eu.dagster.cloud/mcp. It is a beta feature and may change, and it is not available for Dagster OSS.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Launching a run from a conversation
Start it, watch the logs, and terminate if it goes wrong — no way to quietly edit it mid-flight.
02
Materialising an asset on request
Trigger materialisation without granting anything that could delete the asset.
03
Handling an alert
Alert policies and Dagster+ issues have full create, update and delete.
BEFORE YOU INSTALL
What to know first
Requires
- A Dagster+ organization — not available for Dagster OSS
- An MCP client that can reach a remote endpoint
Where it runs
Both documented setups connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.agent.dagster.cloud/mcpRequirements
- OAuth sign-in to Dagster+ in the browser, or a Dagster+ user token sent as Authorization: Bearer together with a Dagster-Cloud-Organization header
MCP Clients
Claude Code — OAuth
CLAUDE CODE — OAUTH · TERMINAL
claude mcp add --transport http dagster-plus https://mcp.agent.dagster.cloud/mcpThen start a claude session, type /mcp, select dagster-plus and choose Authenticate to sign in to Dagster+ in the browser.
Claude Code — User Token
CLAUDE CODE — USER TOKEN · TERMINAL
claude mcp add --transport http dagster-plus https://mcp.agent.dagster.cloud/mcp --header "Dagster-Cloud-Organization: <YOUR_ORGANIZATION>" --header "Authorization: Bearer <YOUR_TOKEN>"<YOUR_ORGANIZATION> is your Dagster organization and <YOUR_TOKEN> a Dagster+ user token.
