Croway commented on PR #8950: URL: https://github.com/apache/camel-quarkus/pull/8950#issuecomment-5179136902
> > WDYT @jamesnetherton @JiriOndrusek > > If it is just literally a case of switching between `quarkus-mcp-server-http` & `quarkus-mcp-server-stdio`, then yes, we could just have the extension depend on `quarkus-mcp-server-core` and users choose the server impl. > > If it's not that simple, then maybe we just go with HTTP initially? I'd go with HTTP, in particular, right now the following is possible: * add the `quarkus-mcp-server-stdio` on the pom.xml * enable stdio via properties `quarkus.mcp.server.stdio.enabled=true` * disable http `quarkus.mcp.server."<default>".http.enabled=false` This works with the current code, and can be documented, it might be a bit hacky, but this way the component is battery included, OOB, http works. -- 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]
