aldettinger opened a new pull request, #9412: URL: https://github.com/apache/camel-quarkus/pull/9412
…. Related to #9342. The MCP Server extension documentation claimed that the stdio transport could be added alongside the extension, and that Camel tools would then be served over both transports simultaneously. Both claims overstate what the extension supports, so the documentation is reworded to describe only the streamable HTTP transport, with an explicit statement that stdio is not supported. The removed stdio instructions were also stale: they pinned quarkus-mcp-server-stdio 1.13.1 while the project now builds against quarkiverse-mcp-server 2.0.3, and the BOM manages only quarkus-mcp-server-http, so following them pulled in a conflicting quarkus-mcp-server-core. Mentions of Camel Main, Camel JBang and Spring Boot are dropped as well. Readers of this page are working on Camel Quarkus, and the cross-runtime pointers added noise without being actionable here. This is a documentation-only change. The extension metadata is untouched, so the catalog mapping from org.apache.camel:camel-mcp-server to org.apache.camel.quarkus:camel-quarkus-mcp-server is unchanged and `camel export --runtime=quarkus` keeps behaving as before. Note that this commit is related to #9342 but does not fix it. -- 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]
