FenjuFu commented on issue #17376: URL: https://github.com/apache/dolphinscheduler/issues/17376#issuecomment-5306317802
This DSIP's MCP use case already has working community implementations that don't wait for an official client — they wrap the existing Open API directly. Sharing one as a reference point for the client discussion: [iflytek/dolphin-mcp-pilot](https://github.com/iflytek/dolphin-mcp-pilot) is an MCP server (Python / FastMCP) exposing DolphinScheduler operations as ~53 structured tools — projects, workflow and DAG creation, schedules, instances, resources, logs, monitoring, plus a raw API passthrough for anything not yet wrapped. It supports API-token or user/password auth, and per-request credentials in HTTP mode for multi-tenant use. It is community-maintained, not an official Apache DolphinScheduler component. It's also a concrete data point for the "which APIs does the client need" question @ruanwenjun raised: the tool surface here is basically the subset of the Open API that agents actually reach for. If an official client/SDK lands, an MCP layer like this becomes a thin adapter over it instead of calling REST directly. I've also opened #18551 / #18552 to document community MCP integrations (this project and ocean-zhc/dolphinscheduler-mcp) under `docs/integration`, as a neutral, non-endorsing entry point. Review welcome. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
