Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

Related Servers

Alternatives to dolphin-mcp-pilot

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Production-ready MCP server for Apache DolphinScheduler. Enables AI agents to operate data workflows end-to-end with 58 tools covering DAG creation, schedule management, instance control, guided troubleshooting, serial backfills, and version rollback.
      58
      24
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to orchestrate AI agents and tasks, inspect DAG workflows, monitor cluster metrics, and perform safe database queries and statements through standardized MCP tools.
      189
      Apache 2.0
    • A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables AI assistants to interact with Apache Airflow's REST API for DAG management, task monitoring, and system diagnostics. It provides comprehensive tools for triggering workflows, retrieving logs, and inspecting system health across Airflow 2.x and 3.x versions.
      31
      13
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to inspect and operate Apache Airflow over its REST API, providing read tools and safe write operations (gated by read-only mode) for managing DAGs, runs, tasks, and pools.
      14
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that wraps the Apache Airflow REST API, enabling clients to manage DAGs, monitor task instances, and handle workflows through a standardized interface. It provides comprehensive access to Airflow features including DAG runs, variables, connections, and XComs.
      MIT

    TDQS

    A3.5/5.0

    Scored across 60 tools

    Disambiguation2/5

    Several tool clusters overlap heavily: ds_create_workflow vs ds_create_dag_workflow (explicitly 'mode 1/mode 2' of the same action), ds_update_task_param vs ds_modify_workflow_dag's update_task vs ds_update_workflow, and ds_force_task_success vs ds_skip_task which both mark a task successful without running it. The long descriptions clarify the boundaries, but an agent still has to reason carefully to pick the right mutation tool, and the raw_* passthroughs compete with the dedicated tools.

    Naming Consistency5/5

    Every tool uses the same ds_ prefix followed by a verb_noun construction (ds_list_workflows, ds_create_project, ds_delete_resource, ds_rerun_from_failure). Naming is uniform across all 60 tools with no camelCase or style mixing, and the ds_ prefix cleanly separates domain tools from helpers like ds_help.

    Tool Count2/5

    60 tools is far beyond a comfortable surface for one server, even for a broad platform like DolphinScheduler covering projects, workflows, DAGs, instances, schedules, resources, monitoring and raw HTTP. The four raw_* passthroughs plus a help tool plus near-duplicate create/modify variants inflate the set; the surface would be stronger consolidated.

    Completeness4/5

    Coverage is genuinely deep: full CRUD on projects, workflows/DAGs, instances, schedules and resources, plus versions/rollback, cloning, backfill, logs, alert config and an escape hatch. Minor gaps remain, such as no user/tenant/worker-group creation and no deletion of individual task instances, but these are workable around via raw tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues