michaaels commented on issue #9052: URL: https://github.com/apache/hop/issues/9052#issuecomment-6309233756
Thanks, @bamaer! Great to hear you're already working on MCP-related improvements for 2.21. Several of these ideas align well with what I've been building. The connector already includes native metadata inspection, dependency analysis, structural validation, and separate opt-in permissions for execution and semantic changes. One important detail is that the MCP server is already implemented as a native Apache Hop plugin, using Hop's existing plugin architecture and APIs. It runs through hop mcp over STDIO, without requiring changes to Hop core. The HTTP/OAuth transport, more granular tool scopes, and integration with AI Advisor would be particularly interesting additions. Since the connector is already structured as a plugin, I think it could serve as a foundation for integrating these new capabilities into Apache Hop while keeping the implementation modular. Do you have a particular architecture in mind for the 2.21 changes? It would be great to align our approaches and see how we can build on the existing implementation. I'm happy to help with the development and contribute through smaller PRs where appropriate. -- 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]
