You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "shahar1 (via GitHub)" <gi...@apache.org> on 2026/07/04 20:41:21 UTC
Re: [PR] Add internal development MCP server for Airflow API as part of Breeze [airflow]
shahar1 commented on PR #69381:
URL: https://github.com/apache/airflow/pull/69381#issuecomment-4883746257
> > We had considered MCP for breeze before as well (I need to recall the context and dig into what we had discussed why not MCP but Agent Skills) or perhaps the purpose of the MCP this PR would like to introduce is different from what we want to achieve in Airflow GSoC Breeze Agent Skills -- #62500.
>
> I would echo what @jason810496 wrote. I think MCP server is only really useful where you want to have some real "server side" content that you want to keep behind the server. Breeze does not really have any "data" behind to expose via MCP only "actions" and I would say SKILLs are much, much better (and cheaper) way of accessing breeze functionality - if we think CLI is not enough.
I feel that there's a misunderstanding here (and I renamed the title, as previous one might have been misleading) -
the MCP is for Airflow REST API which is deployed as part of breeze, not for breeze commands.
I'll be happy if you could read through the use cases, as well as the ADR.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org