domain: docs.dagster.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Locate the Dagster webserver GraphQL endpoint, typically at http://{dagster_host}:{port}/graphql.
Authenticate if required; Dagster Cloud requires an Authorization: Bearer YOUR_TOKEN header, while OSS deployments may be unauthenticated.
Send a POST request with Content-Type: application/json and a body containing a GraphQL mutation such as launchRun, specifying the repositoryLocationName, repositoryName, jobName, and any runConfigData as a YAML string or JSON.
Capture the run.runId from the mutation response.
Poll using the pipelineRunOrError(runId: "RUN_ID") query, checking the status field until it reaches SUCCESS, FAILURE, or CANCELED.
Retrieve run logs via the logsForRun query or the Dagster UI using the runId.
Known gotchas
The GraphQL schema evolves across Dagster versions; confirm the mutation and query field names against the /graphql introspection endpoint for the specific version deployed.
runConfigData must be valid YAML or a matching JSON structure for the job's config schema; invalid config causes the run to fail at validation before any ops execute.
Dagster Cloud uses workspace and deployment scoping; include the correct deployment name in the request path or header as required by the Cloud API.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?