Skip to main content
Glama
Sign In
Aluriak

mcp-dagster

by Aluriak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-dagster

No user-submitted related servers found.

    Related Servers

    • posthog-toolkit-mcp

      deadrime
      A
      license
      A
      quality
      C
      maintenance
      Enables querying PostHog with HogQL, retrieving event and property definitions, session replays, and project lists, plus optional REST API access with safeguards against accidental writes and API key leakage.
      6
      3 npm
      MIT

    • DuckDB MCP Server

      poovenp
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables running read-only SQL queries and exploring DuckDB databases through MCP tools like listing tables, describing schemas, and fetching paginated data.
      -

    • Databricks MCP

      Agent-Hellboy
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only interaction with a Databricks workspace, exposing catalog metadata and bounded SQL querying while preserving caller identity through OAuth-protected authorization.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct resource: instance summary, asset list, single asset state, run list, single run detail, and sensors/schedules. The only soft overlap is dagster_overview, which summarizes runs and schedules that dagster_list_runs and dagster_sensors_schedules also expose, but the descriptions make the summary-vs-detail distinction clear enough.

    Naming Consistency4/5

    All tools share the dagster_ prefix and snake_case, giving a predictable namespace. Most follow a verb_noun shape (list_assets, list_runs, run_detail, asset_state), with dagster_overview and dagster_sensors_schedules being minor deviations but still readable.

    Tool Count5/5

    Six tools is well-scoped for a Dagster observability surface, covering summary, assets, runs, and schedules without redundancy. Every tool earns its place and nothing feels like filler.

    Completeness3/5

    The surface is read-only: there is no way to launch or re-run a job, trigger a backfill (despite backfills being mentioned in the overview), or materialize an asset, and no run logs access. These are notable gaps for an agent trying to act on Dagster, though inspection workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources