Dolphin Mcp Pilot

io.github.iflytek由 GitHub 帳號 iflytek 發布v0.3.1更新於 Nov 3, 2026

AI agent interface to Apache DolphinScheduler: 58 MCP tools for workflow orchestration & data ops.

發布方自己的服務:QuickBooks Connector by Meridian

概覽

AI 產生的概覽

讓 AI 助理操作 Apache DolphinScheduler 的 MCP 伺服器:建立工作流程與 DAG、管理排程、控制實例、查看日誌與資源。

可以做什麼
  • 建立與複製 SQL 或 DAG 工作流程,更新任務參數,回復工作流程版本
  • 管理 cron 排程:建立、上線、下線、刪除
  • 控制流程實例:暫停、恢復、重跑、從失敗處重跑、刪除,以及依日期區間補資料
  • 排查執行狀況:列出流程實例與任務實例、讀取任務日誌、強制任務成功或略過失敗任務
  • 檢視與更新資源內容,並在工具未涵蓋時直接呼叫原始 DolphinScheduler API
  • 透過內建說明工具了解各類任務建議的操作流程
適用情境
適合讓助理在既有的 DolphinScheduler 3.x 環境中執行實際的資料維運工作,例如排查失敗的執行、補跑缺漏日期、建立並排程新的工作流程,而不只是列出與啟停任務。
執行需求
需要一個可連線的 DolphinScheduler 3.x 實例,並在 DS_URL 填入 API 基礎位址。驗證方式為 DS_TOKEN 中的 API 權杖,或 DS_USER 與 DS_PASSWORD 的使用者名稱密碼;DS_TENANT_CODE 可選擇設定租戶。README 的快速開始以 Docker Compose 執行並提供 HTTP MCP 端點,也支援 stdio 模式。
安裝前請注意
它會變更正式環境的排程:相關工具可建立、刪除、暫停、重跑與回復工作流程及實例,強制任務成功,並呼叫任意原始 API。憑證(DS_TOKEN,或 DS_USER 與 DS_PASSWORD)透過環境變數或每次請求的標頭傳入,需妥善保管;多租戶 HTTP 模式下每個呼叫方各自提供憑證。建議先以唯讀請求確認影響範圍。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Dolphin Mcp Pilot,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

dolphin-mcp-pilot

A production-ready MCP server for Apache DolphinScheduler (小海豚).

dolphin-mcp-pilot exposes 53+ tools for projects, workflows, DAG creation, schedules, instances, resources, logs, monitoring and raw API passthrough — designed for AI agents that need to operate DolphinScheduler beyond basic read-only usage.

🎯 Why this project?

Most public DolphinScheduler MCP servers only cover basic read/list/start/stop scenarios. This project is designed for real operations work:

  • ✅ Create SQL / DAG workflows in one line
  • ✅ Manage schedules (create / online / offline / delete)
  • ✅ Control process instances (pause / resume / rerun / rerun-from-failure)
  • ✅ View task logs, force task success / skip failed task
  • ✅ Manage resources (view/update content)
  • ✅ Roll back workflow versions, clone workflows
  • ✅ Use raw API as a safety valve
  • ✅ Support multi-tenant per-request auth

🚀 Key features

  • 53+ tools covering most practical DS operations
  • Two auth modes: API Token (X-DS-Token) or User/Password (X-DS-User + X-DS-Password)
  • Multi-tenant HTTP mode: each caller can use its own credentials
  • MCP 2.0 stateless HTTP with automatic compatibility for MCP 1.x clients
  • Workflow creation: simple SQL and complex DAG workflows with multiple task types
  • Schedule management (cron-based)
  • Instance lifecycle control (pause/resume/rerun/rerun-from-failure/delete)
  • Resource content management and version rollback / workflow clone
  • Raw API passthrough for uncovered edge cases

🚀 Quick Start

Prerequisites

  • A running DolphinScheduler 3.x instance whose API is reachable from Docker
  • Docker with Compose v2 (docker compose version)
  • A DolphinScheduler API token (recommended), or a username and password
bash
# 1. Clone the repositorygit clone https://github.com/iflytek/dolphin-mcp-pilot.gitcd dolphin-mcp-pilot
# 2. Configure environmentcp .env.example .env# Edit .env — set DS_URL and DS_TOKEN (or DS_USER/DS_PASSWORD)# Example DS_URL: http://your-dolphinscheduler-host:12345/dolphinscheduler
# 3. Build and start the service from this checkoutdocker compose --profile dev up -d dolphin-mcp-pilot-dev
# 4. Confirm that the container is healthydocker compose --profile dev ps

The MCP endpoint is now http://localhost:8001/mcp/ (the trailing slash is required). Add it to an HTTP/SSE-capable MCP client:

json
{  "mcpServers": {    "dolphinscheduler": {      "type": "sse",      "url": "http://localhost:8001/mcp/",      "headers": { "X-DS-Token": "your_api_token" }    }  }}

As a safe first check, ask your agent: “List my DolphinScheduler projects and workflows. Do not make any changes.” For client-specific configuration and username/password auth, see Client Config.

💡 Common use cases

ScenarioExample requestMain tools
Investigate a failed run“Find the latest failed workflow, show the failed task and its log, and suggest the next action without changing anything.”ds_list_process_instances, ds_list_task_instances, ds_get_latest_failure_log
Backfill missing data“Backfill 2026-08-01 through 2026-08-07 serially, starting from the validation task and including downstream tasks.”ds_complement_data
Create and schedule a workflow“Create a daily SQL workflow, add its cron schedule, and show me the definition before putting it online.”ds_create_workflow, ds_set_schedule, ds_online_schedule
Give multiple agents controlled accessRun one HTTP MCP service while each caller supplies its own DolphinScheduler credentials.Per-request X-DS-* headers

The tools can also pause, resume, rerun, clone, and roll back workflows; manage resources; and fall back to raw DolphinScheduler APIs for uncovered operations. Start with ds_help(category="quickstart") inside your MCP client to discover the recommended workflow for each task.

📚 Documentation

DocumentDescription
📦 InstallationDocker Compose (dev/prod), from source, as package, run modes
⚙️ ConfigurationEnvironment variables, auth options, Compose tunables
🚀 DeploymentProduction deployment, Compose reference, verify, troubleshoot
📊 FeaturesFeature comparison table, tool categories
🔐 Client ConfigMCP client setup (CodeBuddy, Claude Desktop, etc.), multi-tenant auth
📖 API ReferenceAll 53+ tools, parameter conventions, error handling (中文)
❓ FAQCommon issues and solutions (中文)

✨ What's new

  • MCP 2.0: supports the stateless 2026-07-28 protocol while keeping legacy handshake clients and stdio configurations working.
  • Guided troubleshooting: ds_list_process_instances attaches a next_action hint to RUNNING/FAILURE instances, pointing agents to ds_list_task_instances to inspect individual task nodes.
  • Reliable backfill ordering: serial complement uses the complementStartDate/complementEndDate range format so DolphinScheduler generates instances in strict day-by-day order.
  • Flexible task params: ds_update_task_param accepts both snake_case and camelCase field names and reports ignored fields.

🤝 Contributing

Contributions are welcome. See CONTRIBUTING.md for project changes, or follow the example contribution guide to share a tested MCP client configuration.

Used dolphin-mcp-pilot for something real? Write it up in cases/ — a gallery of community usage stories (agent-driven DolphinScheduler ops), each linked to a public post.

📄 License

Apache-2.0

🙏 Acknowledgments

Built with the official MCP Python SDK and inspired by the Apache DolphinScheduler community.

來源:README.md,提交 7aeb3ea

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.3.1最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Pilot 整合