mcp-dagster
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_repositoriesA | List all available Dagster repositories |
| list_jobsB | List all jobs in a specific repository |
| list_assetsB | List all assets in a specific repository |
| recent_runsC | Get recent Dagster runs |
| get_run_infoC | Get detailed information about a specific run |
| launch_runC | Launch a Dagster job run |
| materialize_assetC | Materialize a specific Dagster asset |
| terminate_runA | Terminate an in-progress Dagster run |
| get_asset_infoB | Get detailed information about a specific asset |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: listing repositories, jobs, assets; getting run/asset info; and actions like launch/terminate/materialize. There is no ambiguity between tools.
Most tools follow a verb_noun pattern (list_*, get_*, launch_run, terminate_run, materialize_asset), but 'recent_runs' breaks the pattern as an adjective-noun phrase. This is a minor deviation.
9 tools is well-scoped for a Dagster server covering repositories, jobs, assets, and runs. It provides necessary operations without being excessive.
The surface covers listing and getting info for key entities, plus launching/terminating runs and materializing assets. A minor gap is the lack of get_job_info or more granular run listing, but core workflows are supported.