Dolphin MCP Pilot

Name: Dolphin MCP Pilot
Author: iflytek

by iflytekversion 0.3.1i★ –iRuns on your computer

Registry nameio.github.iflytek/dolphin-mcp-pilot

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Other
You need to fill in: DS_URL

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: DS_URL, DS_TOKEN, DS_USER, DS_PASSWORD, DS_TENANT_CODE

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "dolphin-pilot": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DS_URL",
        "-e",
        "DS_TOKEN",
        "-e",
        "DS_USER",
        "-e",
        "DS_PASSWORD",
        "-e",
        "DS_TENANT_CODE",
        "ghcr.io/iflytek/dolphin-mcp-pilot:0.3.1"
      ],
      "env": {
        "DS_URL": "your-value",
        "DS_TOKEN": "your-value",
        "DS_USER": "your-value",
        "DS_PASSWORD": "your-value",
        "DS_TENANT_CODE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add dolphin-pilot --env DS_URL=your-value --env DS_TOKEN=your-value --env DS_USER=your-value --env DS_PASSWORD=your-value --env DS_TENANT_CODE=your-value -- docker run -i --rm -e DS_URL -e DS_TOKEN -e DS_USER -e DS_PASSWORD -e DS_TENANT_CODE ghcr.io/iflytek/dolphin-mcp-pilot:0.3.1

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "dolphin-pilot": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DS_URL",
        "-e",
        "DS_TOKEN",
        "-e",
        "DS_USER",
        "-e",
        "DS_PASSWORD",
        "-e",
        "DS_TENANT_CODE",
        "ghcr.io/iflytek/dolphin-mcp-pilot:0.3.1"
      ],
      "env": {
        "DS_URL": "your-value",
        "DS_TOKEN": "your-value",
        "DS_USER": "your-value",
        "DS_PASSWORD": "your-value",
        "DS_TENANT_CODE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "dolphin-pilot": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DS_URL",
        "-e",
        "DS_TOKEN",
        "-e",
        "DS_USER",
        "-e",
        "DS_PASSWORD",
        "-e",
        "DS_TENANT_CODE",
        "ghcr.io/iflytek/dolphin-mcp-pilot:0.3.1"
      ],
      "env": {
        "DS_URL": "your-value",
        "DS_TOKEN": "your-value",
        "DS_USER": "your-value",
        "DS_PASSWORD": "your-value",
        "DS_TENANT_CODE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

DS_URL required env
DolphinScheduler API base URL (e.g. http://localhost:12345/dolphinscheduler)
DS_TOKEN env
DolphinScheduler API token (leave empty to use DS_USER/DS_PASSWORD instead)
DS_USER env
DolphinScheduler username (alternative to DS_TOKEN)
DS_PASSWORD env
DolphinScheduler password (used with DS_USER)
DS_TENANT_CODE env
Tenant code (default: 'default')

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account iflytek, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32700 servers in this category
Published to the registry more recently than 31% of the other 32700 servers in this category
Basic checks equal to or better than 100% of the other 32700 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Dolphin MCP Pilot safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: DS_URL

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Agent Data Tools: Utilities

by Nutshell2000

103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Scenario	Example request	Main 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 access	Run 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

Document	Description
📦 Installation	Docker Compose (dev/prod), from source, as package, run modes
⚙️ Configuration	Environment variables, auth options, Compose tunables
🚀 Deployment	Production deployment, Compose reference, verify, troubleshoot
📊 Features	Feature comparison table, tool categories
🔐 Client Config	MCP client setup (CodeBuddy, Claude Desktop, etc.), multi-tenant auth
📖 API Reference	All 53+ tools, parameter conventions, error handling (中文)
❓ FAQ	Common 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.

Dolphin MCP Pilot

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Agent Data Tools: Utilities

README from the maker

dolphin-mcp-pilot

🎯 Why this project?

🚀 Key features

🚀 Quick Start

Prerequisites

2. Configure environment

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

4. Confirm that the container is healthy

💡 Common use cases

📚 Documentation

✨ What's new

🤝 Contributing

📄 License

🙏 Acknowledgments