kaxil commented on PR #69381: URL: https://github.com/apache/airflow/pull/69381#issuecomment-4895014748
> > @abhishekbhakat you worked on [a related project](https://github.com/abhishekbhakat/airflow-mcp-server) - any feedback you can share to improve this feature will be most welcome! > > I would just leave this here: > > > "Skills" are for a generic do it all agent whereas "MCP" is for agents with specific scope. There is no point load MCP of all the different services an agent can connect to, that's what skills are for. But a specialized agent need not to load the skill every new conversation when MCP serves the purpose (_can have dynamic set of tools and be state maintaining, skills can also do that but would use a couple of extra hops_). Both are here to co-exist. > > Also, I would like everyone here to think about updates delivery. For MCP, it is straightforward; it ships with the product. But for skills, you'll have to keep reminding the user to keep updating them. And what happens for backwards compatibility? Waste more tokens to know oh this doesn't work in this version? Which will be seemless with MCP. We are working as part of Skills over MCP group: https://modelcontextprotocol.io/community/working-groups/skills-over-mcp#membership to create a spec to deliver Skills as part of MCP. Although, the PR here is for Adding MCP to Breeze for development purposes, so delivery / versioning is moot. -- 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]
