Dolphin Pilot MCP server

dolphin-mcp-pilot

English | 简体中文

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

# 1. Clone the repository
git clone https://github.com/iflytek/dolphin-mcp-pilot.git
cd dolphin-mcp-pilot

# 2. Configure environment
cp .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 checkout
docker compose --profile dev up -d dolphin-mcp-pilot-dev

# 4. Confirm that the container is healthy
docker 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:

{
  "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

Shortened. The full README is on GitHub.