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 集成