zbendhiba commented on issue #8706: URL: https://github.com/apache/camel-quarkus/issues/8706#issuecomment-6172820879
I worked on this and ended up reframing the approach. PR coming shortly. The original idea was to point agents at the Camel JBang MCP server. The PR takes a different route: - I don't want Quarkus users to install and run a second MCP server. The Quarkus Agent MCP is not just an app launcher: it brings the whole environment around dev mode and the Dev UI : live reload, Dev Services, continuous testing, .... That is the ecosystem Camel Quarkus should plug into. - The Camel JBang MCP server remains a great option, especially for Camel users prototyping with the Camel CLI. It is just a different developer experience, centered on Camel JBang. For a Quarkus application, the natural home for agent tooling is the Quarkus dev mode. The docs page in the PR mentions it as a complement for people working with both runtimes. So the plan: self-contained quarkus-skill.md files shipped by the extensions themselves (starting with camel-quarkus-core and camel-quarkus-bean), plus Dev MCP tools in the core extension for live catalog lookup and endpoint URI validation, backed by the application's own RuntimeCamelCatalog. One MCP server, zero extra setup. -- 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]
