abhishekbhakat commented on PR #69381: URL: https://github.com/apache/airflow/pull/69381#issuecomment-4895246471
> I am a proponent of Remote/Server-side MCP for various reasons that I added in https://kaxil.substack.com/p/mcp-vs-cli-vs-rest . But I'd take a different route, if the end goal is AIP-91 :) -- i.e. not start with Breeze. But that's completely my POV. Agreed that Breeze falls into the “developer with terminal access” bucket, not the “remote/server-side MCP” bucket. Also agreed `airflowctl` should become more agent-friendly, but I don’t think that should block an opt-in MCP implementation that is already contributor-driven and scoped. But once it lands in Airflow, it becomes official surface area. Even if contributor-led, affects maintenance, focus, and drives the direction of Airflow’s agent story. So PMC members should decide. 😅 Personally, I tend to use both, specialized subagents with MCP and skill with the orchestrator. Saves a lot of tokens for me. -- 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]
