Dagster MCP (fabdendev)

70/100

Capped at 70: core tools not tested: no backing service on the test box; the tests add up to 90. Why scores are capped

Last tested 2026-11-13 UTC (Fresh: tested within 30 days) Connects · tools listedNo tool call tested yet No key to connect

Advisories: not yet checked

Security review: not tested

Test points add up to 90; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (90/100)

  • Install20/20
  • Handshake30/30
  • Maintenance15/25
  • Docs15/15
  • License10/10

Tested pypi dagster-mcp 0.12.3 (MIT; repo fabdendev/dagster-mcp). Installed pinned with scripts off (uv venv, Python 3.13) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 17 tools (no tool annotations). Real calls: 0 of 3 real function calls passed. No passing real call: needs a running Dagster instance. Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. No passing real call: needs a running Dagster instance. Evidence: local test run, Nov 13, 2026 UTC.

Transport (tested 2026-11-13 UTC): stdio

Token cost (estimate): approx. 3645 tokens, cl100k estimate (17 tools, measured 2026-11-13 UTC, version 0.12.3). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 17 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • get_asset_details — read
  • get_asset_health — read
  • get_instance_status — read
  • get_recent_materializations — read
  • get_run_failure_summary — read
  • get_run_logs — read
  • get_run_stats — read
  • get_run_status — read
  • get_runs — read
  • get_tick_history — read
  • list_backfills — read
  • list_code_locations — read
  • list_jobs — read
  • list_schedules — read
  • list_sensors — read
  • resolve_asset_selection — read
  • search_assets — read

handshake and tools listed without a recorded key or OAuth

Score 70/100 · Tools 17 · Token cost approx. 3,645 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 0.12.3 · Package dagster-mcp · Repo fabdendev/dagster-mcp

Summary: Dagster MCP (fabdendev) completed an MCP handshake without credentials and exposed 17 tools.

Evidence summary

Handshake
pass
Tools listed
17
Context cost
approx. 3645 tokens, cl100k estimate (17 tools, measured 2026-11-13 UTC, version 0.12.3; an estimate) ranking · add up your servers' context cost
API key
No key to connect (handshake passed)
Tested
2026-11-13 UTC

Test results

TestResultPointsEvidence
installpass20uv pip install dagster-mcp (Python venv, Linux) succeeded in 1s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 17 tools listed in 2.9s.
maintenancepartial15Repo pushed 45 days before test.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 3645 tokens, cl100k estimate for 17 tools · about 44% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-13 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 17 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

d38e667fd611: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "dagster-mcp",
  "version": "0.12.3",
  "registry": "pypi",
  "status": "working",
  "tested": "2026-11-13",
  "tools_count": 17,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`uv pip install dagster-mcp` (Python venv, Linux) succeeded in 1s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 17 tools listed in 2.9s."
    ],
    "maintenance": [
      "partial",
      15,
      "Repo pushed 45 days before test."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

uvx dagster-mcp

Pin the version we tested

uvx dagster-mcp==0.12.3

pip install dagster-mcp==0.12.3

tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "dagster-mcp-fabdendev": {
      "command": "uvx",
      "args": [
        "dagster-mcp==0.12.3"
      ]
    }
  }
}

Tools listed

get_runs, get_run_status, get_run_logs, get_run_stats, get_run_failure_summary, get_recent_materializations, get_asset_details, search_assets, resolve_asset_selection, get_asset_health, list_jobs, list_schedules, list_sensors, get_tick_history, list_code_locations, get_instance_status, list_backfills

Quick config

{
  "mcpServers": {
    "dagster-mcp-fabdendev": {
      "command": "uvx",
      "args": [
        "dagster-mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run uv pip install dagster-mcp (Python venv). This is the exact command we ran on 2026-11-13 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (17 in our test).
{
  "mcpServers": {
    "dagster-mcp-fabdendev": {
      "command": "uvx",
      "args": [
        "dagster-mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

FAQ

Is Dagster MCP (fabdendev) deprecated?

No. dagster-mcp was not deprecated or archived when we last tested it on 2026-11-13 UTC.

What replaces Dagster MCP (fabdendev)?

Nothing; Dagster MCP (fabdendev) is not deprecated as of 2026-11-13 UTC.

Does Dagster MCP (fabdendev) need an API key?

No. It completed an MCP handshake with no credentials and listed 17 tools.

Embed the badge

TestedMCP: 70/100, tested 2026-11-13 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue