Dolphin Mcp Pilot

io.github.iflytekPublished by GitHub account iflytekv0.3.1Updated Nov 3, 2026

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

The publisher's own server: QuickBooks Connector by Meridian

Overview

AI-generated overview

MCP server that lets an AI assistant operate Apache DolphinScheduler: create workflows and DAGs, manage schedules, control instances, read logs and resources.

What you can do
  • Create and clone SQL or DAG workflows, update task parameters, roll back workflow versions
  • Manage cron schedules: create, bring online, take offline, delete
  • Control process instances: pause, resume, rerun, rerun from failure, delete, and backfill date ranges
  • Inspect runs: list process and task instances, read task logs, force task success or skip failed tasks
  • View and update resource content, and call raw DolphinScheduler APIs for uncovered cases
  • Discover recommended workflows through a built-in help tool
When to use it
Useful when an assistant should do real data-ops work on an existing DolphinScheduler 3.x deployment: investigating failed runs, backfilling missing dates, or creating and scheduling new workflows, rather than only listing and starting jobs.
Requirements
A reachable DolphinScheduler 3.x instance and its API base URL in DS_URL. Authentication is either an API token in DS_TOKEN or a username and password in DS_USER and DS_PASSWORD; DS_TENANT_CODE optionally sets the tenant. The README's quick start runs it as a Docker Compose service exposing an HTTP MCP endpoint, and it can also run over stdio.
Before you install
It can change production scheduling: tools create, delete, pause, rerun and roll back workflows and instances, force tasks to success, and call arbitrary raw APIs. Credentials (DS_TOKEN or DS_USER with DS_PASSWORD) are supplied by environment variable or per-request headers, so protect them. In multi-tenant HTTP mode each caller passes its own credentials. Start with read-only requests to confirm scope.

Installation

In SourceWeft

  1. Open Dolphin Mcp Pilot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 7aeb3ea

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Pilot integrations